JET and GCJ?

Started by PlanetMongo, July 20, 2003, 14:38:26

Previous topic - Next topic

PlanetMongo

Hi Cas:
I've read that you use JET to produce Win32 executables with decent (great?) success, but you are looking to move away from JET.  May I ask why?

I think you alluded to cross-platform issues (but then again, if you already have a licensed JET, wouldn't it make sense to use what you can for the platforms at hand?), but just wanted to confirm.

Secondly, has anyone looked into the completely of GCJ as of yet and for its suitability for producing cross-platform native binaries?  I looked through their website and noticed there's work yet to be done, but is it complete enough (or will it be complete enough?) to work for LWJGL and basic games development?  For instance, AWT is not completed yet, but LWJGL doesn't use AWT.  I wonder if the bare minimum is working... I know the windows version is a bit lagging, as well, but if  you have JET, then you could build with JET for Win32 and maybe look into GCJ for linux and other platforms..

http://gcc.gnu.org/java/status.html is a reference page for you to look through if you haven't already.

Maybe I'm clueless, though.  :)
ife sucks, kill yourself.

AndersD

Last time I checked it didn't work ( ~ two months ago, co from cvs). Not sure what the problem was - maybe just that the (gcj) compiler was too buggy atm.

But most of the java.nio package files did indeed have an implementation (only one "byte order" though - can't  remember which), so it shouldn't be too long until it's complete. Why don't you give it a try? :)

EDIT: and static linking didn't work at all.

princec

An obsession with "free" might end up with you having to use a crock of shit of course :) Some things are just worth what they cost, and Jet's worth what it costs.

I would move away from Jet but there simply is no alternative. Jet does what I want it to do; it just needs improving a little (all those problems I had with internationalization for example). JetPerfect's the real culprit - it's tricky to use and difficult to get it right.

Cas :)