Path: utzoo!attcan!uunet!mcvax!hp4nl!philmds!leo
From: leo@philmds.UUCP (Leo de Wit)
Newsgroups: comp.lang.c
Subject: Re: Cake (was Recursive #includes)
Message-ID: <971@philmds.UUCP>
Date: 5 Mar 89 12:24:32 GMT
References: <9752@smoke.BRL.MIL> <238@yasc.PLA.CA.US> <20078@santra.UUCP>
Reply-To: leo@philmds.UUCP (Leo de Wit)
Organization: Philips I&E DTS Eindhoven
Lines: 30

In article <20078@santra.UUCP> alo@hut.fi (Antti Louko) writes:
|When I saw cake first time, it seemed just fine. But after a while I
|realized one thing. After that I haven't used cake anymore.
|
|Lets have an Cakefile:
|
|$ cat Cakefile
|vax:	/dev/null
|	cp /dev/null vax
|
|$ cake
|cp /dev/null 1
|$
|
|Funny, uh? If you have a SUN, replace "vax" with "sun".

How about undefining some predefined macros?
This one is for Ultrix 2.0:

/lib/cpp -Uunix -Ubsd4_2 -Uultrix -Uvax -U__LINE__ -U__FILE__ makefile

Of course, if you want to use those names also for conditional make
rules inclusion, you're out of luck. But so you are if you try to
declare 'vax' as a variable in a C program! From this viewpoint and
to enhance cakefile portability I would prefer to leave them #defined
and refrain from using targets like 'vax', etc.

(B.T.W. I found those macros using 'strings -2 /lib/cpp')

    Leo.