Re: Compiling Gnome ?

[Raja R Harinath <harinath cs umn edu>]

Andrew Veliath <andrewtv@usa.net> writes:
> ..--==-  23 Jul 1998 10:39:06 -0600,
> ..--==-  Tom Tromey (TT) discussed:
>  )))))) "Andrew" == Andrew Veliath <andrewtv@classic.netaddress.com>
>  )))))) writes:
>  Andrew)  Hm.  This is interesting.  The reason I didn't use
>  Andrew)  AC_PROG_CPP is because it tends to give me 'gcc -E' which
>  Andrew)  didn't seem useful here.
> 
>  TT)  Actually, it turns out that this is what you want.
> 
>  TT)  Some systems might not have "/lib/cpp" or any other cpp
>  TT)  executable.  Instead, the preprocessor might be integrated into
>  TT)  the compiler.  In this case the only way to run the preprocessor
>  TT)  is by running "cc -E".
> 
>  TT)  In the future it is likely that gcc will be built this way (to
>  TT)  get better performance) -- the code to integrate cpp with the
>  TT)  body of the compiler already exists.
> 
> Well, I changed it to use AC_PROG_CPP (I had actually written more
> tests in the meantime to check for cpp in other places, but in lieu of
> this I removed those).  Since it requires a .c file, I symlinked it to
> a temporary file and then had it read that.  It seems to work for the
> most part at the moment, but only testing will tell.

You may want to test if `$(CPP) $(CPPFLAGS) -' works as a filter, i.e.,
works on stdin.  `gcc -E -' scans stdin.  Piping through stdin feels
cleaner than symlinking to a temporary .c file.

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash