This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
[ecj] Patch: FYI: document --enable-java-maintainer-mode
- From: Tom Tromey <tromey at redhat dot com>
- To: Java Patch List <java-patches at gcc dot gnu dot org>
- Date: 19 Dec 2006 11:05:55 -0700
- Subject: [ecj] Patch: FYI: document --enable-java-maintainer-mode
- Reply-to: tromey at redhat dot com
I'm checking this in on the gcj-eclipse-merge-branch.
This documents --enable-java-maintainer-mode in install.texi.
I think I've finally reached the end of my to-do list for the merge.
However I would appreciate it if someone else could look at the
documentation and say whether it looks sufficient. Also, if you know
of a merge task that I've missed, that would help as well.
Tom
Index: ChangeLog
from Tom Tromey <tromey@redhat.com>
* doc/install.texi (Configuration): Document
--enable-java-maintainer-mode.
Index: doc/install.texi
===================================================================
--- doc/install.texi (revision 120056)
+++ doc/install.texi (working copy)
@@ -1422,6 +1422,14 @@
@subsubheading General Options
@table @code
+@item --enable-java-maintainer-mode
+By default the @samp{libjava} build will not attempt to compile the
+@file{.java} source files to @file{.class}. Instead, it will use the
+@file{.class} files from the source tree. If you use this option you
+must have executables named @samp{ecj1} and @samp{gjavah} in your path
+for use by the build. You must use this option if you intend to
+modify any @file{.java} files in @samp{libjava}.
+
@item --with-java-home=@var{dirname}
This @samp{libjava} option overrides the default value of the
@samp{java.home} system property. It is also used to set