This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: GCJ and $PREFIX/include revisited
- From: Tom Tromey <tromey at redhat dot com>
- To: Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: java at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: 18 Dec 2003 09:47:42 -0700
- Subject: Re: GCJ and $PREFIX/include revisited
- References: <Pine.BSF.4.53.0305041319370.41531@acrux.dbai.tuwien.ac.at><87llxjki7o.fsf@fleche.redhat.com><Pine.BSF.4.58.0312142309250.76198@acrux.dbai.tuwien.ac.at>
- Reply-to: tromey at redhat dot com
>>>>> "Gerald" == Gerald Pfeifer <gerald@pfeifer.com> writes:
Gerald> The c++ headers are now nicely versioned, in c++/3.4/, but the java
Gerald> headers still are put directly into $PREFIX. How about doing something
Gerald> like java/3.4 or gcj/3.4 in parallel to c++?
Gerald> And do we really need ffi.h and jvmpi.h there?
While talking with a couple folks about this on irc, I realized I
don't understand why we don't change the layout a bit to get versioned
headers for everything all at once.
I.e., instead of $(includedir)/c++/$(version), $(includedir)/gcj/$(version),
etc, why not make $(includedir)/$(version)/ as the base, and then
install headers directly under that?
There's a couple benefits to this. One is that we don't need to add a
new built-in -I option when we move the java heaers. Another is that
if we ever add another target library, we'll have an understandable
explanation of where to put its header files.
Tom