java-gnome-developer

[Java-gnome-developer] java gnome vs. pkg-config

[Dalibor T. <ro...@ka...>]

Hi all,

due to Mark Wielaard calling out for people to test java-gnome with 
their VMs, I've decided to try out java-gnome from CVS with kaffe from 
CVS. Unfortunately, I didn't get very far, but I managed to spot some 
problems ;)

1) The README file refers the user to an INSTALL file. There is no 
INSTALL file in the java-gnome CVS top level directory. But there is one 
in common/INSTALL. I could submit a patch, if you need one ;)

2) There is no configure script, and it doesn't seem to be documented 
how to generate it. I've came up with the grand idea of running
genConfigure.in, genMakefile.in and autoreconf, but that should be 
documented in the INSTALL file ;) Again, I could submit a patch, if 
necessary.

3) Finally, my configure run breaks due to

bash-2.05a$ ./configure --with-kaffe 
--with-kaffe-prefix=/tmp/topic/current-jit3/
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for a BSD-compatible install... /usr/bin/install -c
Add /tmp/topic/current-jit3//bin to path and check again.
checking for kaffe... /tmp/topic/current-jit3//bin/kaffe
checking for Kaffe - Java Version >= 1.1... yes
checking for javadoc... /tmp/topic/current-jit3//bin/javadoc
checking for javac... /tmp/topic/current-jit3//bin/javac
checking for kaffe... /tmp/topic/current-jit3//bin/kaffe
checking for jar... /tmp/topic/current-jit3//bin/jar
checking for main in -libs... no
checking for pkg-config... /usr/bin/pkg-config
checking for gtk+-2.0 >= 2.2... Package gtk+-2.0 was not found in the 
pkg-config search path.
Perhaps you should add the directory containing `gtk+-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gtk+-2.0' found

configure: error: Library requirements (gtk+-2.0 >= 2.2) not met; 
consider adjusting the PKG_CONFIG_PATH environment variable if your 
libraries are in a nonstandard prefix so pkg-config can find them.

I have no idea what `gtk+-2.0.pc' is or where I can find it. Any 
pointers or ideas where to search for the file?

4) The FAQ says that you're looking for someone who's been using kaffe 
to compile things to help out. Well, here I am ;)

I've discussed the build failures Mark had with him on IRC, and I think 
currently, the problem when using kaffe's java compiler is that it 
doesn't know about the -sourcepath option. A way to fix that would be to 
avoid using -sourcepath altogether, and simply cd into the directory. 
Another way would be to (LN_S) the source files into a build dir, and 
compile from there.

All that being said, I look forward to run java-gnome apps on kaffe, 
since I think gnome & java would mix well. All the best wishes for 
getting into the official GNOME binding set.

cheers,
dalibor topic

Re: [Java-gnome-developer] java gnome vs. pkg-config

[Mark H. <mh...@ca...>]

Hi,

On Tue, Dec 16, 2003 at 03:59:30PM +0100, Dalibor Topic wrote:
> due to Mark Wielaard calling out for people to test java-gnome with 
> their VMs, I've decided to try out java-gnome from CVS with kaffe from 
> CVS.
Excellent, thanks.

Please note that I have moved most of the directories in cvs in the last
few days to comply with gnome bindings release rules. I've also had to
rewrite much of the configure and makefile system. Since we create
multiple tarballs, the configure and makefiles are now generated using
the ./gen* scripts, copying common sections from the common directory.


> 1) The README file refers the user to an INSTALL file. There is no 
> INSTALL file in the java-gnome CVS top level directory. But there is one 
> in common/INSTALL. I could submit a patch, if you need one ;)
The tarball building tool will copy the documents to the toplevel
directory for each tarball

I did create a new readme documenting the changes. Unfortunately it's
been overwritten by the old one. Thank's for spotting that. I will
create a README.cvs file explaining a few of these new things.

> 2) There is no configure script, and it doesn't seem to be documented 
> how to generate it. I've came up with the grand idea of running
> genConfigure.in, genMakefile.in and autoreconf, but that should be 
> documented in the INSTALL file ;) Again, I could submit a patch, if 
> necessary.
./genConfigure.in
./genMakefile.in
autoconf
same problem as above

> 3) Finally, my configure run breaks due to
> 
> bash-2.05a$ ./configure --with-kaffe 
> --with-kaffe-prefix=/tmp/topic/current-jit3/
> I have no idea what `gtk+-2.0.pc' is or where I can find it. Any 
> pointers or ideas where to search for the file?

You need to have gtk development libraries installed. This is an package
named something like libgtk2.0-dev

> 4) The FAQ says that you're looking for someone who's been using kaffe 
> to compile things to help out. Well, here I am ;)
> 
> I've discussed the build failures Mark had with him on IRC, and I think 
> currently, the problem when using kaffe's java compiler is that it 
> doesn't know about the -sourcepath option. A way to fix that would be to 
> avoid using -sourcepath altogether, and simply cd into the directory. 
> Another way would be to (LN_S) the source files into a build dir, and 
> compile from there.
I think I fixed that in cvs earlier today - by using the CLASSPATH
environment variable, although this has not been verified with kaffe
yet. We cannot simply cd to the directory since there are multiple
directories

> All that being said, I look forward to run java-gnome apps on kaffe, 
> since I think gnome & java would mix well. All the best wishes for 
> getting into the official GNOME binding set.

That's excellent news. The more JVMs the better. I did try with kaffe
once before (with my bugwatcher program, debian package debbuggtk), but
jni support wasn't good enough. 

thanks

-- 
  .''`. Mark Howard
 : :' :
 `. `'  http://www.tildemh.com 
   `-   mh...@de... | mh...@ti... | mh...@ca... 

Re: [Java-gnome-developer] java gnome vs. pkg-config

[Mark W. <ma...@kl...>]

Hi,

On Tue, 2003-12-16 at 16:19, Mark Howard wrote:
> > All that being said, I look forward to run java-gnome apps on kaffe,=20
> > since I think gnome & java would mix well. All the best wishes for=20
> > getting into the official GNOME binding set.
>=20
> That's excellent news. The more JVMs the better. I did try with kaffe
> once before (with my bugwatcher program, debian package debbuggtk), but
> jni support wasn't good enough.=20

When I first tried to get the snark-gnome frontend to work with kaffe I
made a little JNI patch for kaffe:
http://www.kaffe.org/pipermail/kaffe/2003-July/042990.html
This should be in recent versions (kaffe>=3D1.1.1).

Cheers,

Mark

Re: [Java-gnome-developer] java gnome vs. pkg-config

[Luca De R. <pie...@li...>]

Il mar, 2003-12-16 alle 15:59, Dalibor Topic ha scritto:
> Hi all,
> 
> due to Mark Wielaard calling out for people to test java-gnome with 
> their VMs, I've decided to try out java-gnome from CVS with kaffe from 
> CVS. Unfortunately, I didn't get very far, but I managed to spot some 
> problems ;)
> 
> 1) The README file refers the user to an INSTALL file. There is no 
> INSTALL file in the java-gnome CVS top level directory. But there is one 
> in common/INSTALL. I could submit a patch, if you need one ;)
> 
> 2) There is no configure script, and it doesn't seem to be documented 
> how to generate it. I've came up with the grand idea of running
> genConfigure.in, genMakefile.in and autoreconf, but that should be 
> documented in the INSTALL file ;) Again, I could submit a patch, if 
> necessary.
> 
> 3) Finally, my configure run breaks due to
> 
> bash-2.05a$ ./configure --with-kaffe 
> --with-kaffe-prefix=/tmp/topic/current-jit3/
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for a BSD-compatible install... /usr/bin/install -c
> Add /tmp/topic/current-jit3//bin to path and check again.
> checking for kaffe... /tmp/topic/current-jit3//bin/kaffe
> checking for Kaffe - Java Version >= 1.1... yes
> checking for javadoc... /tmp/topic/current-jit3//bin/javadoc
> checking for javac... /tmp/topic/current-jit3//bin/javac
> checking for kaffe... /tmp/topic/current-jit3//bin/kaffe
> checking for jar... /tmp/topic/current-jit3//bin/jar
> checking for main in -libs... no
> checking for pkg-config... /usr/bin/pkg-config
> checking for gtk+-2.0 >= 2.2... Package gtk+-2.0 was not found in the 
> pkg-config search path.
> Perhaps you should add the directory containing `gtk+-2.0.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'gtk+-2.0' found
> 
> configure: error: Library requirements (gtk+-2.0 >= 2.2) not met; 
> consider adjusting the PKG_CONFIG_PATH environment variable if your 
> libraries are in a nonstandard prefix so pkg-config can find them.
> 
> I have no idea what `gtk+-2.0.pc' is or where I can find it. Any 
> pointers or ideas where to search for the file?
On some distributions it can be found in the gtk2-devel package. The
file should be located in $LIBDIR/pkgconfig. Mine looks like:
$ cat /usr/lib/pkgconfig/gtk+-2.0.pc 
prefix=/usr
exec_prefix=/usr
libdir=/usr/lib
includedir=/usr/include
target=x11

gtk_binary_version=2.2.0
gtk_host=i386-redhat-linux-gnu

Name: GTK+
Description: GIMP Tool Kit (${target} target)
Version: 2.2.1
Requires: gdk-${target}-2.0 atk
Libs: -L${libdir} -lgtk-${target}-2.0 
Cflags: -I${includedir}/gtk-2.0 

It contains compiler flags and other needed things.

> 
> 4) The FAQ says that you're looking for someone who's been using kaffe 
> to compile things to help out. Well, here I am ;)
Great, I'm managing to compile j-g with free tools only, so I could
count on your help ;)

> 
> I've discussed the build failures Mark had with him on IRC, and I think 
> currently, the problem when using kaffe's java compiler is that it 
> doesn't know about the -sourcepath option. A way to fix that would be to 
> avoid using -sourcepath altogether, and simply cd into the directory. 
> Another way would be to (LN_S) the source files into a build dir, and 
> compile from there.
Mark, it seems that using the CLASSPATH variable does the job.

> All that being said, I look forward to run java-gnome apps on kaffe, 
> since I think gnome & java would mix well. All the best wishes for 
> getting into the official GNOME binding set.
Thanks :)

-- 
Luca De Rugeriis <pie...@li...>