koala

[Richard Dale]

On Wednesday 17 April 2002 11:32 pm, Bernd Gehrmann wrote:
> Is there some recipe to quickly regenerate the java source
> files in javasupport? It's quite tragic that this stuff breaks
> each time a library class is changed :-(
The tool used to generate the bindings is 'kdebindings/kalyptus', usage:

$ kalyptus -fjava <gideon plugin api headers>

As well as the gideon headers, it might need the classes that they inherit 
from (for event handling callbacks for instance). So a safer usage is:

$ kalyptus -fjava <gideon plugin api headers + Qt headers + kdelibs headers>

And discard any unwanted sources generated.

I keep a patch of any manual edits needed for the previous version, and apply 
that to the newly generated sources. It would be nice to completely automate 
it, but I'm not sure if it's possible (cf kdebindings/kdejava often fails to 
build too). Possibly the unedited sources could go in the cvs under an 
'AUTOGENERATED_BINDINGS' tag, so that the manual edits would be the 
difference between this and the HEAD branch.

I really would like to document this process well enough so that someone other 
than myself could do it. The README in the kalyptus directory is the only 
documentation so far.

But I'll check out the current KDevelop/Gideon and bring the java api up to 
date again soon.

I would like to switch to compiling javasupport to gcj/native code, rather 
than jvm bytecodes, as that fits in better with the KDE build and runtime 
environment. The KDE generated libtool doesn't seem to work with gcj though, 
and arts doesn't compile with gcc 3.1.

-- Richard