Santiago Vila wrote: > I plan to create the Debian gettext > package using this call to the configure script: > > JAVAC=jikes-classpath ./configure --prefix=/usr --disable-csharp
Looks good, yes. (Except for the --disable-csharp: do you have problems with pnet?) > By "if gcj is present, gettext will install an executable which does > not need a jar", do you mean that I should better keep gcj as a > build-dependency even if I already have jikes-classpath? That depends how you wish to have the runtime dependencies. If you have gcj in the PATH during the build, the package will need /usr/lib/libgcj.so.3 at runtime. If you don't have gcj in the PATH during the build, the package will need a JVM at runtime (e.g. gij + /usr/share/java/libgcj-3.4.3.jar). > Will jikes-classpath be enough to generate the .jar's? I hope so, yes. > Will they be correct for all architectures? Yes. jars are architecture independent. > In case I need it, what would be the most simple way to check that the > created .jar's are ok? [ I would like not to repeat the mistake of > providing a .jar which does not work ]. You can check the libintl.jar by configuring and running the installed examples/hello-java/ sample. If a gettext.jar is generated, you can check it by looking at the testsuite result of gettext-tools/tests/msgunfmt-java-1. Bruno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
