🚀 go-pugleaf

In article <1992Dec9.015113.2141@Trirex.COM> dglattin@trirex.com (Dennis  
Glatting) writes:
] In article <1f3badINN1lr@darkstar.UCSC.EDU> isbell@cats.ucsc.edu (Art  
] Isbell) writes:
] > 
] > In article <1992Nov25.173006.638@gamelan> thf@zelator.in-berlin.de  
] (Thomas Funke) writes:
] > >Be careful: If you hack the original header-files, you have to  
] recompile the  
] > >precompiled headers (*.p), because otherwise the compiler will not use  
] them  
] > >anymore. VERY SLOW compilations then ! (20 Seconds for 
] > >#include <appkit/appkit.h> )
] > 
] > Thomas makes an excellent point, here.  You might consider compiling  
] with the
] > PB "Args:" field set to "OTHER_CFLAGS=-Wprecomp" occasionally.  This  
] will show
] > you whether precompiled headers are actually being used.
] 
] 
] You might consider not using the GNU preprocessor but rather make a  
] symlink to the NeXT one.  This may reduce the amount of compiler related  
] issues and still give you what you want from cc1, cc1obj, etc.
] 

If you do this, you will not be able to build or use libg++ 2.2.2 or the  
equivalent.  The Gnu preprocessor knows how to handle the #include_next  
directive (no relation to "NeXT"), and the NeXT version cannot.

--
Douglas Scott                              (805)893-8352
Center for Computer Music Research and Composition
University of California, Santa Barbara
Internet: (NeXTMail ok)   <doug@foxtrot.ccmrc.ucsb.edu>