Re: 3.3.1 GCJ Cross compiler configuration issues

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Peter" == Peter Blemel <pblemel@hotmail.com> writes:

Peter> Which brings me to another issue ;-)  For an embedded system with no
Peter> display and no network support it just takes up space to build awt /
Peter> swing / etc classes.    These groups of classes are tacked onto the
Peter> end of 'ordinary_java_source_files'.   Is it advisable to make a
Peter> change such as
Peter> @NATIVE_TRUE@awt_SOURCES = $(awt_java_source_files)
Peter> java_source_files = ... $(awt_SOURCES)
Peter> ?

You can certainly try it.  There's a patch on the gui branch that
separates the libraries a bit more, something like that might it
easier to do this.

You may run into problems since the Java libraries generally have lots
of inter-dependencies.  I'd imagine most of AWT and Swing will drop
out without much work though.  You may need AWTPermission.

Another approach is to use static linking, which in theory will just
omit anything that isn't used.

This whole subject comes up quite a bit on the gcj list.  Nobody has
really solved it in a definitive way.  We're really waiting for
someone with the need and the drive to do it.

Peter> Which brings me to another point.   When building from a 'stock' GCC
Peter> distribution everything (including .java files) are recompiled many
Peter> times (ca, le, nof, und).   Is there a particular reason that the
Peter> .class files need to be built so many times?

You've got multilibs enabled.  Sometimes you don't really need this,
e.g. with my old PowerBook I just configure with --disable-multilibs
and speed up the build.

Whether or not you need them, I don't know.  But if you do need
multilibs, then unfortunately you just have to live with the
recompilations.  It wouldn't be very easy to set up the build to share
.class files but not anything else.

Tom