This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi People, This patch adds a section on Java-specific libgcj configure options as requested by Tom Tromey here: http://gcc.gnu.org/ml/java-patches/2003-q4/msg00670.html Tom looked at the first draft of this here and elaborated on some of the options: http://gcc.gnu.org/ml/java-patches/2004-q1/msg00265.html Note that since the initial incarnation of the patch, I also added an explicit subheading for cross-compiler-specific options in order to be consistent with the new subheading for Java-specific ones. Tom: I incorporated your suggestions and also took the liberty of adding your name to the patch because of them. I slightly embellished these descriptions w.r.t. your suggestions: +@item --enable-interpreter +Enable the Java interpreter. The interpreter is automatically +enabled by default on all platforms that support it. This option +is really only useful if you want to disable the interpreter +(using @option{--disable-interpreter}). +@item --disable-java-net +Disable java.net. This disables the native part of java.net only, +using non-functional stubs for native method implementations. Finally, Michael Koch pointed out off-list that multiple AWT peer implementations may be specified. As such, I changed the documentation for --enable-java-awt to the following: +@item --enable-java-awt=PEER(S) +Specifies the AWT peer library or libraries to build alongside +@samp{libgcj}. If this option is unspecified or disabled, AWT +will be non-functional. Current valid values are @option{gtk} and +@option{xlib}. Multiple libraries should be separated by a +comma (i.e. @option{--enable-java-awt=gtk,xlib}). As before, I've attached the bzipped generated gccinstall.html if you're interested. -- Mohan http://www.thisiscool.com/ http://www.animalsong.org/ ChangeLog 2004-01-27 Mohan Embar <gnustuff@thisiscool.com> Tom Tromey <tromey@redhat.com> * doc/install.texi: Moved --disable-libgcj and --with-system-zlib documentation to new section for Java-specific options. Added explicit Cross-Compiler-Specific Options subheading. Added section for Java-specific options. Index: doc/install.texi =================================================================== RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v retrieving revision 1.248.4.3 diff -u -2 -r1.248.4.3 install.texi --- doc/install.texi 18 Jan 2004 11:59:06 -0000 1.248.4.3 +++ doc/install.texi 28 Jan 2004 03:38:07 -0000 @@ -546,4 +546,8 @@ work and should not normally be used. +Note that each @option{--enable} option has a corresponding +@option{--disable} option and that each @option{--with} option has a +corresponding @option{--without} option. + @table @code @item --prefix=@var{dirname} @@ -1011,16 +1015,4 @@ language sub-directories might not have been configured! -@item --disable-libgcj -Specify that the run-time libraries -used by GCJ should not be built. This is useful in case you intend -to use GCJ with some other run-time, or you're going to install it -separately, or it just happens not to build on your particular -machine. In general, if the Java front end is enabled, the GCJ -libraries will be enabled too, unless they're known to not work on -the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you -may need to port it; in this case, before modifying the top-level -@file{configure.in} so that @samp{libgcj} is enabled by default on this platform, -you may use @option{--enable-libgcj} to override the default. - @item --with-dwarf2 Specify that the compiler should @@ -1116,8 +1108,4 @@ libiconv library files in @file{@var{dir}/lib}. -@item --with-system-zlib -Use installed zlib rather than that included with GCC@. This option -only applies if the Java front end is being built. - @item --enable-obsolete Enable configuration for an obsoleted system. If you attempt to @@ -1131,5 +1119,6 @@ @end table -Some options which only apply to building cross compilers: +@subheading Cross-Compiler-Specific Options +The following options only apply to building cross compilers. @table @code @item --with-sysroot @@ -1179,7 +1168,139 @@ @end table -Note that each @option{--enable} option has a corresponding -@option{--disable} option and that each @option{--with} option has a -corresponding @option{--without} option. +@subheading Java-Specific Options + +The following option applies to the build of the Java front end. + +@table @code +@item --disable-libgcj +Specify that the run-time libraries +used by GCJ should not be built. This is useful in case you intend +to use GCJ with some other run-time, or you're going to install it +separately, or it just happens not to build on your particular +machine. In general, if the Java front end is enabled, the GCJ +libraries will be enabled too, unless they're known to not work on +the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you +may need to port it; in this case, before modifying the top-level +@file{configure.in} so that @samp{libgcj} is enabled by default on this platform, +you may use @option{--enable-libgcj} to override the default. + +@end table + +The following options apply to building @samp{libgcj}. + +@subsubheading General Options + +@table @code +@item --disable-getenv-properties +Don't set system properties from @env{GCJ_PROPERTIES}. + +@item --enable-hash-synchronization +Use a global hash table for monitor locks. Ordinarily, +@samp{libgcj}'s @samp{configure} script automatically makes +the correct choice for this option for your platform. Only use +this if you know you need the library to be configured differently. + +@item --enable-interpreter +Enable the Java interpreter. The interpreter is automatically +enabled by default on all platforms that support it. This option +is really only useful if you want to disable the interpreter +(using @option{--disable-interpreter}). + +@item --disable-java-net +Disable java.net. This disables the native part of java.net only, +using non-functional stubs for native method implementations. + +@item --disable-jvmpi +Disable JVMPI support. + +@item --with-ecos +Enable runtime eCos target support. + +@item --without-libffi +Don't use @samp{libffi}. This will disable the interpreter and JNI +support as well, as these require @samp{libffi} to work. + +@item --enable-libgcj-debug +Enable runtime debugging code. + +@item --enable-libgcj-multifile +If specified, causes all @file{.java} source files to be +compiled into @file{.class} files in one invocation of +@samp{gcj}. This can speed up build time, but is more +resource-intensive. If this option is unspecified or +disabled, @samp{gcj} is invoked once for each @file{.java} +file to compile into a @file{.class} file. + +@item --with-libiconv-prefix=DIR +Search for libiconv in @file{DIR/include} and @file{DIR/lib}. + +@item --enable-sjlj-exceptions +Force use of @code{builtin_setjmp} for exceptions. @samp{configure} +ordinarily picks the correct value based on the platform. Only use +this option if you are sure you need a different setting. + +@item --with-system-zlib +Use installed @samp{zlib} rather than that included with GCC@. + +@item --with-win32-nlsapi=ansi, unicows or unicode +Indicates how MinGW @samp{libgcj} translates between UNICODE +characters and the Win32 API. +@table @code +@item ansi +Use the single-byte @code{char} and the Win32 A functions natively, +translating to and from UNICODE when using these functions. If +unspecified, this is the default. + +@item unicows +Use the @code{WCHAR} and Win32 W functions natively. Adds +@code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}. +@file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines +running built executables. @file{libunicows.a}, an open-source +import library around Microsoft's @code{unicows.dll}, is obtained from +@uref{http://libunicows.sourceforge.net/}, which also gives details +on getting @file{unicows.dll} from Microsoft. + +@item unicode +Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not} +add @code{-lunicows} to @file{libgcj.spec}. The built executables will +only run on Microsoft Windows NT and above. +@end table +@end table + +@subsubheading AWT-Specific Options + +@table @code +@item --with-x +Use the X Window System. + +@item --enable-java-awt=PEER(S) +Specifies the AWT peer library or libraries to build alongside +@samp{libgcj}. If this option is unspecified or disabled, AWT +will be non-functional. Current valid values are @option{gtk} and +@option{xlib}. Multiple libraries should be separated by a +comma (i.e. @option{--enable-java-awt=gtk,xlib}). + +@item --enable-gtk-cairo +Build the cairo Graphics2D implementation on GTK. + +@item --enable-java-gc=TYPE +Choose garbage collector. Defaults to @option{boehm} if unspecified. + +@item --disable-gtktest +Do not try to compile and run a test GTK+ program. + +@item --disable-glibtest +Do not try to compile and run a test GLIB program. + +@item --with-libart-prefix=PFX +Prefix where libart is installed (optional). + +@item --with-libart-exec-prefix=PFX +Exec prefix where libart is installed (optional). + +@item --disable-libarttest +Do not try to compile and run a test libart program. + +@end table @html
Attachment:
gccinstall.html.bz2
Description: application/bzip2
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |