[3826] in Kerberos
Re: Kerberos V4: Linking a new library
daemon@ATHENA.MIT.EDU (Mike Friedman (510) 642-1410)
Mon Sep 12 21:59:47 1994
To: kerberos@MIT.EDU
Date: Mon, 12 Sep 94 16:06:42 PDT
From: spgmnf@cmsa.Berkeley.EDU (Mike Friedman (510) 642-1410)
In article <9409121355.AA25260@vantage.vantage>
cc32859@vantage.fmrco.com (Donald Sharp) writes:
>I'm in the throes of understanding the new krb5b4p2 autoconf system,
>and I don't have the V4 source tree handy right now, but I somewhat
>remember how this works. Imake.rules and Imake.tmpl (along with
>Project.rules and Project.tmpl, if any) define the macros that expand
>into Makefiles. The inputs that provide the parameters that control
>how them macros expand are found in the *.def files. I suggest
>looking in site.def and/or osconf.def in the src/config directory.
>
Well, what I have is not a config, but a util directory. The only files
in it, however, are Imake.rules and Imake.template, plus config.Imakefile
(the basic Imake configuration that I've tailored for my environment) and
the generated Makefile. I don't see any 'Project' files, nor any of the
other files you mention.
Only Imake.rules seems to have a 'rule' for generating objects from sources.
The only thing that confuses me is that there are two parts: one for object
files that go in the current directory and one for object files apparently
destined for a 'profiled' directory. The profiled directory, however, is now
empty, so I don't know if I need to worry about that portion of the rule.
Here's the entire 'c.o' rule in Imake.rules:
$(CC) PROF_FLAG -c $(CFLAGS) $*.c
$(MV) $*.o profiled/$*.o
$(CC) -c $(CFLAGS) $*.c
-$(LD) -x -r -o a.out $*.o
$(MV) a.out $*.o
I could change the first and third statement above. Is that all I would
have to do?
Thanks.
