This is the mail archive of the
mailing list for the Java project.
Things libgcj hackers should know
- To: java-discuss at sources dot redhat dot com
- Subject: Things libgcj hackers should know
- From: Mark Wielaard <mark at klomp dot org>
- Date: Thu, 25 Jan 2001 17:39:49 +0100
Would it be an idea to add a HACKING file to the libjava directory with
the following content?
A lot of the standard library files come from the GNU Classpath project.
The libgcj and Classpath project have officially merged, but the merge
is not yet complete. Our eventual goal is for Classpath to be an upstream
source provider for libgcj, however it will be some time before this becomes
reality: libgcj and Classpath have different implementations of many core
java classes. In order to merge them, we need to select the best (most
efficient, cleanest) implementation of each method/class/package, resolve
any conflicts created by the merge, and test the final result.
The merged files can be recognized by the standard Classpath copyright
comments at the top of the file. If you make changes to these files then
you should also send a patch to the classpath mailinglist.
If you merge a libgcj class with a classpath class then you must update the
copyright notice at the top of the file so others can see that this is a
shared libgcj/classpath file.
If you need to add new java files to libgcj then you have to edit the
Makefile.am file in the top (libjava) directory. And run automake.
But note the following (thanks to Bryce McKinlay):
> Do you know the magic dance I have to do when adding them to Makefile.am
> so they will appear in Makefile.in and finally in the user generated
Yup, you need the magic libgcj automake ;-)
Install that (dont worry, it should still work for other projects), add your
files to the Makefile.am, then just type "automake" and it will regenerate the
There are probably lots of other things that should be explained in such a
HACKING file, but this is at least a start.