fitzsim at redhat.com
Sun Jun 17 12:08:33 PDT 2007
Andrew John Hughes wrote:
> On Saturday 16 June 2007 18:46, Mark Wielaard wrote:
>> Hi Andrew,
>> On Fri, 2007-06-15 at 21:21 +0100, Andrew John Hughes wrote:
>>> To cut a long story short, I've succeeded in cobbling together a small
>>> autoconf build system that will pluck through the OpenJDK sources and
>>> build them (just javac, javadoc, javah and apt so far, as a proof of
>>> concept -- but more should be easy enough to add now the main work's
>>> done). It creates a tools.jar and scripts to run them (just like those
>>> in Classpath). I was wondering if it would be worth me cleaning this up
>>> a little (adding niceties like a README, etc.) and hosting it with the
>>> rest of the IcedTea stuff.
>> Nice. This sounds very useful. How "portable" is the result? Is it
>> completely self-contained or do the tools depend on some of the internal
>> openjdk library implementations (can I use them with gcj for example)?
> It seems portable. Personally, I run the resulting tools with cacao and GNU
> Classpath and it has worked fine so far. I've just managed to build most of
> JikesRVM using the tools.jar (Ant tries to use this by default, which is what
> inspired me in the first place). I've also succeeded in compiling apt to
> native from the result, but it failed to run due to my gcj being outdated (it
> doesn't have the javac hacks we added yet) -- I need to build a new one at
> some point.
Have you thought about simply merging the OpenJDK tools sources you need
into the GNU Classpath repository, under the tools/external directory?
Then all the GNU Classpath-using runtime projects would have convenient
access to these tools without any extra merging effort.
More information about the distro-pkg-dev