I just saw Ranjit Mathew's diary, Miscellany, and the status of GCJ attracts me, so that I decided to take a try with GCJx. I wrote a small build script, which can automatically check out from CVS, build GCJX, and show you if it's completed or not.
GCJX worked very well with my test cases, and I even modified kaffe/libraries/javalib/Makefile.am.in to drive GCJX generating bytecode for Kaffe's API implementations. It seems to work, but I think I should take a look over the existing build process, according to kaffe/library/javalib/Makefile.am:
# Note: Makefile.am is generated from Makefile.am.in using # developers/update-class-list (called from developers/autogen.sh) # # Yes, it's slightly insane: # # Makefile.am.in -> Makefile.am -> Makefile.in -> MakefileAlso, I found the kaffeawt building fault of Nano-X AWT backend. It would be better to introduce new rules for generating the separate jarball.
Ooops, I have to say again, GCJX rocks. Kudos to Tom Tromey!
FOAF updates: Trust rankings are now exported, making the data available to other users and websites. An external FOAF URI has been added, allowing users to link to an additional FOAF file.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!