zzhu8192
Still Fresh
I managed to build a cross-compiling version of gcc 4.1.0 with gcj working for the gp2x with Linux as host. I used native calls to implement drawing to screen, and managed to get a sample program to work on my gp2x. I'll post the instructions here or on the wiki if there is interest, especially from Java developers.
After the binary is stripped, a hello world type app is about 5.6 megs.
This is statically linked. For some reason, dynamically linked apps don't work, even when I put all the libs on the sd card and used LD_LIBRARY_PATH.
I haven't tried to write anything performance intensive, but GCJ seems to do a pretty good job. Allocations and gc speed is not great, but seems to work.
One odd thing I've run into, is that the x86 target version of gcc 4.1.0/gcj for linux produces code (even hello world) that seg faults instantly when statically linked. (dyna link works fine) The irony here is the cross-compiler with target ARM920 works fine with -static when compiled on Linux. Anyone else run into this issue? I'm running on Slackware 10.2.
After the binary is stripped, a hello world type app is about 5.6 megs.
This is statically linked. For some reason, dynamically linked apps don't work, even when I put all the libs on the sd card and used LD_LIBRARY_PATH.
I haven't tried to write anything performance intensive, but GCJ seems to do a pretty good job. Allocations and gc speed is not great, but seems to work.
One odd thing I've run into, is that the x86 target version of gcc 4.1.0/gcj for linux produces code (even hello world) that seg faults instantly when statically linked. (dyna link works fine) The irony here is the cross-compiler with target ARM920 works fine with -static when compiled on Linux. Anyone else run into this issue? I'm running on Slackware 10.2.