build macros and includes

Mon Oct 4 04:35:00 GMT 2004

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Montag, 4. Oktober 2004 01:42 schrieb Ray Auge:
> Hello All,
>> I'm currently trying to resolve a problem with java-gnome and gcj.
>> I have two things I'd like cleared up. Must we locate libgcj.jar
> and add it to the classpath or do we assume that gcj will pick the
> correct jar on a system with multiple versions? i.e. Mandrake 10.1
> bundles both libgcj-3.3.2.jar and libgcj-3.4.1.jar .
>> The result is that in the java-gnome configure step when a query
> for the location of libgcj-?.?.?.jar is made, via "locate", we get
> two versions and the configure fails.

You don't need to locate it at all as gcj doesn't need it at all when 
compiling to native (and then libgcj.so is used like other libraries 
for other apps) and gij should handle it quite well. If not, its a 
bug.
> I'd like to know if this check is even required.
>> Second, due to the nature of java-gnome it often requires the use
> of jni.h. I'd like to know if the gcj team provides a m4 macro that
> can be used to find it or do we simply always assume that it is
> located at /usr/include/libgcj-${gcjversion}/, or is this mostly
> system dependant?

On Debian systems its installed as /usr/include/jni.h and package 
dependencies make sure that only one version of the libgcj devel 
packages is installed (e.g. only libgcj 3.4.2). What you should do is 
to use pkg-config and use the .pc file provided. I think it was first 
included in 3.4.0. I don't know if you wanna support older versions 
of GCJ at all.
Michael
- -- 
Homepage: http://www.worldforge.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBYNSCWSOgCCdjSDsRAmjNAJ0Wfb1yZcd5SRj+7H22/23XzlUpcgCfQLUY
713H/0A4YIVbJ6zWnFonB+A=
=nXKw
-----END PGP SIGNATURE-----