John Leuner <[EMAIL PROTECTED]> writes:
> Well in my case it would be nice to be able to tell the Makefile to build
> a .so library that I can just link in with a normal UNIX executable. But
> what I'm planning for my VM is also to deploy it as the kernel of an
> experimental OS (where dynamic linking may not be available), and in this
> case it would be nice to just a .a file to link to.
You can specify --enable-static to configure if you want to build
static libs. By default we only build dynamic libs. See configure
--help for more information. We don't support the PKGS part of
--enable-static=[PKGS]... I don't even know what that would be. :)
I've tested enabling --enable-static and leaving the dynamic stuff in
default mode and both .so and .a are generated on a 'clean' build, ie
run 'make clean' first.
> When I say 'separate' compilation I mean without compile-time dependencies
> on the JVM (except perhaps header files like jni.h) and on the level of
> each subdirectory (ie java.io, java.net etc).
Java compilation requires compiling all of the java stuff due to
interdependencies up the whazoo. Our current VM dependencies are
jni.h, a vmi (virtual machine interface), and the stuff in
vm/reference/* which maps to Japhar and might need modification for
your particular VM. If you only want to build the stuff in
native/java.net then you should probably cd into classpath/lib and
type 'make' and cd into classpath/native/java.net and type 'make'. I
expected the separate compilation to mean more or less the ability to
install only piece parts of classpath with 'make install java.net' or
something similar.
Brian
--
Brian Jones <[EMAIL PROTECTED]>
