From 484e85e1078cf2f8b8477ce9c279d84b1ffbdefb Mon Sep 17 00:00:00 2001 From: tromey Date: Sun, 21 Aug 2005 23:24:58 +0000 Subject: [PATCH] * HACKING: Updated for hacking classpath in libgcj. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@103324 138bc75d-0d04-0410-961f-82ee72b054a4 --- libjava/ChangeLog | 4 ++++ libjava/HACKING | 24 ++++++++++++++++++++++++ 2 files changed, 28 insertions(+) diff --git a/libjava/ChangeLog b/libjava/ChangeLog index e3c9a6d..4adaf58 100644 --- a/libjava/ChangeLog +++ b/libjava/ChangeLog @@ -1,3 +1,7 @@ +2005-08-21 Tom Tromey + + * HACKING: Updated for hacking classpath in libgcj. + 2005-08-20 John David Anglin PR libgcj/21692 diff --git a/libjava/HACKING b/libjava/HACKING index 410b1cc..649a161 100644 --- a/libjava/HACKING +++ b/libjava/HACKING @@ -60,6 +60,30 @@ However, there are two (known) exceptions to this rule: -- +You can develop in a GCC tree using a CVS checkout of Classpath, most +of the time. (The exceptions are when an incompatible change has been +made in Classpath and some core part of libgcj has not yet been +updated.) + +The way to set this up is very similar to importing a new version of +Classpath into the libgcj tree. In your working tree: + +* cd gcc/libjava; rm -rf classpath +* cvs co classpath +* cd classpath + Now run the auto tools as specified in the import process; then + cd .. +* Run 'scripts/makemake.tcl > sources.am' in the source tree +* Run automake for libgcj + +Now you should be ready to go. + +If you are working in a tree like this, you must remember to run +makemake.tcl and automake whenever you update your embedded classpath +tree. + +-- + If you add a class to java.lang, java.io, or java.util (including sub-packages, like java.lang.ref). -- 2.7.4