This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: Patch: preprocessing infrastructure
- To: "Anthony Green" <green at redhat dot com>
- Subject: Re: Patch: preprocessing infrastructure
- From: Tom Tromey <tromey at redhat dot com>
- Date: 01 Jul 2001 17:03:01 -0600
- Cc: <green at cygnus dot com>, <java-patches at gcc dot gnu dot org>
- References: <200107010421.VAA30955@fencer.cygnus.com> <02a101c1025b$c9c9a740$5be6b4cd@cygnus.com>
- Reply-To: tromey at redhat dot com
>>>>> "Anthony" == Anthony Green <green@redhat.com> writes:
Anthony> I just realized that this only works for natives. Is there
Anthony> any convenient way to create programs for the build machine
Anthony> at this point?
Nope. autoconf and automake are weak on this.
I think using cpp is a mistake anyway. My reason is that the cpp
developers tell us over and over not to use cpp for non-C/C++ uses.
And, we've seen in the past that they are willing to change cpp to
benefit C and C++ at the risk of breaking other users. Finally I
think we don't want to even open the door to #include. So I think we
ought to just make our own mini preprocessor, perhaps using awk.
Tom