Re: [Java-gnome-developer] Re: "Java-GNOME Con 1"

[Jeff M. <ku...@gm...>]

On Tue, 29 Mar 2005 17:47:17 -0500, Ben Konrath <be...@ba...> wrote:
> Hi,
> 
> I'd like to take the opportunity to invite those of you who can't actually
> make it to Toronto. It would be great to see some people meet up on irc
> for some hacking as well :)
> 
> I'm going to start building my gnome stack soon. For those who are
> planning on helping out (in person or on IRC) it would be very useful to
> have gnome stack built before Saturday morning.
> 
> Jeff, do you have your jhbuild conf posted anywhere?

I am attaching my .jhbuildrc file to this email.  There are two items
to be aware of.  The details of each follows:

1) jhbuild has not been updated to support the new java-gnome
structure where each module is a separate project in cvs.  Further
we have recently split out our base classes and jni utility routines
into their own small library to make it easier to support bindings
that do not derive from glib (like cairo-java).  This is also not reflected
in jhbuild.  This means that you can use jhbuild to create the environment
you need to develop java-gnome but you cannot use jhbuild to
build the java-gnome bindings.  If you use eclipse for development
this is not a problem.  You can just check out the code and hack
away.  If you use other tools you could easily check out the java-gnome
modules (more on this later) into your srcdir for jhbuild and hack
hack.

2) You must make a decision on your moduleset prior to starting your 
build.  The gnome-2.12 moduleset still uses gtk+ 2.6 but our libgtk-java 
cvs HEAD uses gtk+ 2.7.  If you plan to work on libgtk-java, cairo-java, 
or our new gst-java bindings you will need to use the gtk28 moduleset.
If you plan to work on any of the other binding projects you must use
the gnome-2.12 moduleset.  My .jhbuildrc file is setup so you can just
comment/uncomment out the correct moduleset and modules.


HOW TO BUILD JAVA-GNOME
----------------------------------------------
Currently our gtk-java, and cairo-java bindings are in heavy development
while our gnome-java, gconf-java, and glade-java bindings are in a stable
(non-development) period.  We have made structural changes to the modules
in development.  Due to these changes there are currently two ways in
 which you would build java-gnome.  This will change once our other modules
enter development and the first method mentioned below will be the only
method.

1) If you wish to build gtk-java and cairo-java for development you should
build the following modules in this order (remember you need jhbuild gtk28
moduleset for this):

gnome cvs: java-gnome
freedesktop cvs: cairo-java
gnome cvs: libgtk-java

2) If you wish to build the entire java-gnome stack (stable releases) for
bug fixing you should build the following modules in this order:

gnome cvs: libgtk-java branch gtk-java-2-6
gnome cvs: llibgnome-java
gnome cvs: libglade-java
gnome cvs: libgconf-java

There are other modules that are part of java-gnome which are quite hackable!
You should follow build order 2 above.  These modules are:

gnome cvs: libgnomevfs-java
gnome cvs: libgtkmozembed-java
gnome cvs: libvte-java

and soon:

freedesktop cvs: gst-java
freedesktop cvs: dbus-java


I look forward to a great time in Toronto this weekend.  In addition
to a healthy dose of hacking there are several key items we will
be discussing which will have an impact on the bindings.  If you
cannot attend please join us on irc.

-- 
Jeffrey Morgan

"The highest reward for a man's toil is not
what he gets for it, but what he becomes by it"
    - Jon Ruskin