[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC: add --enable-libjava-build option

From: Mark Wielaard
Subject: Re: RFC: add --enable-libjava-build option
Date: Wed, 05 Oct 2005 10:07:32 +0200

On Tue, 2005-10-04 at 06:57 +0200, Andreas Tobler wrote:
> as mentioned by Mark and Tom, this should be discussed on the list.
> When we build classpath inside libgcj we 'need' some gcc specific bits 
> to build qt-peers for example. Other areas might benefit too.
> To build c++ stuff we need the just bootstrapped g++, its include & its 
> libraries. To make these known to the classpath machinery it would be 
> good to have the option mentionend in the subject.
> Then we can add the includes and the library to the QT_CFLAGS/QT_LIBS 
> with simply cheking for ENABLE_LIBJAVA_BUILD=yes and add them. (We would 
> have to extend the configury to check for this later, yes)
> So far I see no possibility to pass them down from libjava build into 
> classpath build without the option below.
> What are your comments, thoughts on this? Is there a better possibility?

I am a bit afraid having such a --enable-libjava-build will mean that
lots and lots of tiny hacks are introduced all over the place especially
for the integrating inside gcc case. Which is important. But we have
other projects also integrating classpath. And hopefully we can share
the "integration workarounds" with such project, such as kaffe. So I am
much more in favor of introducing generic solutions for the individual
problems instead of one catch all configure flag.

Could you post your solution for the above QT_CFLAGS/QT_LIBS check using
this ENABLE_LIBJAVA_BUILD? Then we can see if the solution as a whole
can be made generic.



Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]