NetNews Usenet Archive 1992 #30/NN_1992_30.iso/spool/comp/sys/next/programm/7744

Internet Message Format | 1992-12-14 | 1.9 KB

Path: sparky!uunet!news.claremont.edu!ucivax!news.service.uci.edu!unogate!mvb.saic.com!network.ucsd.edu!ucsbcsl!foxtrot.ccmrc.ucsb.edu
From: [e-mail] (Douglas Scott)
Newsgroups: comp.sys.next.programmer
Subject: Re: gcc 2.3.1 on NeXTStep 3.0 ????
Message-ID: <[e-mail]>
Date: 15 Dec 92 00:32:32 GMT
References: <[e-mail]>
Sender: [e-mail]
Reply-To: [e-mail]
Distribution: usa
Lines: 35

In article <[e-mail]> [e-mail] (Dennis
Glatting) writes:
] In article <[e-mail]> [e-mail] (Art
] Isbell) writes:
] >
] > In article <1992Nov25.173006.638@gamelan> [e-mail]
] (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                              [phone]
Center for Computer Music Research and Composition
University of California, Santa Barbara
Internet: (NeXTMail ok)   <[e-mail]>