[Fwd: [Java-gnome-developer] [Help] Autoconf developer wanted]

[Mark Wielaard <mark at klomp dot org>]

Hi,

Since I am a big fan of the java-gnome project I would like to see
someone help them out with their build process. If someone has enough
knowledge about these things please consider helping them out.

java-gnome already supports gcj and uses it for "compiling java source
files to java bytecode and native code (with gcj), compiling c source
files (jni files) and also packaging everything into a jar file and
shared libraries."

But at this moment it is not possible to build java-gnome with just
gcc/gcj installed. The need a different javac compiler or kaffe present
for the build. See the complete call for help for more details.

Cheers,

Mark

--- Begin Message ---

• From: Mark Howard <mh344 at cam dot ac dot uk>
• To: java-gnome-developer at lists dot sourceforge dot net
• Date: Tue, 10 Feb 2004 15:14:08 +0000
• Subject: [Java-gnome-developer] [Help] Autoconf developer wanted

Hello,
  
The Java-Gnome project produces a set of bindings of the core Gnome
developer platform for the Java language. We have recently joined the
official Gnome Bindings Release and as part of this have made a large
overhaul of our repository structure and build system. We have a working
build system but none of us are experts or even experienced in the GNU
autoconf/make tools so there are a few areas where we could do with
help.

Our current build process:
From our repository, we release an all-in-one tarball, plus several
separate tarballs (one for each module). Each tarball has it's own
configure script and make files. Since these have many sections in
common, we generate the actual Makefile.in and configure.in files from
shared files and *.in.in files using a very simple perl script.

The makefiles themselves then compile java-gnome, which involves
compiling java source files to java bytecode and native code (with gcj),
compiling c source files (jni files) and also packaging everything into
a jar file and shared libraries. This part of the build process works
well.

What we want help with:
(in decreasing order of priority)

Modifying the configure script so that any java compiler can be used. At
the moment, we default to javac and allow kaffe with a configure time
option. GNU autoconf-archive has a macro which is supposed to do this,
but unfortunately I couldn't get it to work (it wasn't setting the
JAVA_CFLAGS variable).  Instead, we're using a macro which is very
inflexible and looks like it is a hack of a hack.

For the separate module tarballs, e.g. libgnome-java, we need to locate
libraries which would have been produced by the other tarballs, such as
libgtk2.5-java.so. At the moment, these are hand coded to the default
installation locations. It would be good if this could be configurable.

It would be helpful if we had more parts of the process configurable.
For example, if we could say configure --nodocs so that documentation
does not get generated.

In general, having somebody who knows what they're doing look over our
build system and suggesting any improvements which could be made would
be very reassuring


If you have experience with the standard GNU tools, we really would like
to hear from you. Any help you may offer would be very much appreciated.
A little knowledge of java would be helpful but is in no way necessary.
We will be able to give lots of help if you need it.


-- 
  .''`. Mark Howard
 : :' :
 `. `'  http://www.tildemh.com 
   `-   mh@debian.org | mh@tildemh.com | mh344@cam.ac.uk 

Attachment: signature.asc
Description: Digital signature

--- End Message ---

Attachment: signature.asc
Description: This is a digitally signed message part