After all this talk about java, I tried compiling sablevm in scratchbox to see how much trouble that would be and to see what might need to be hildonized. <br><br>I was able to configure and compile the sablevm sdk package (jikes, fastjar, sablevm, sablevm-classpath) in the i386 side of scratchbox, once I had compiled and installed
libltdl.so library (found in /usr/share/libtool). I was pleasantly surprised to see that when running a small awt application with a textarea boxand a button, the popup keyboard came up when editing in the text box. In Xephyr at least no colormap problems show. I imagine that they will show up on the 770, as sablevm is using a GNU Classpath derivation.
<br><br>However when I tried to duplicate what I had done in the ARM side of scratchbox, I found that I cannot compile libltdl.so as a shared library only as a static library. Without the libltdl library, the sablevm configure script will not proceed as it needs (obviously all java's do) to be able to dynamically load libraries and thinks that it can't. I also found out that I needed to specify the -host and -target on the configure scripts as you do when in a cross compiler system. Perhaps I am wrong , but I thought that under scratchbox ARM, cross compilation should not be needed, as it's running under the QEMU emulator and it should think it's a native ARM environment. Also in none of the maemo documentation does it mention having to specify target and host.
<br>jikes and fastjar compile and create arm binaries.<br><br>So is it normal to have to specify the host and target when using configure in scratchbox ARM? <br>Or should I just wipe scratchbox and reinstall because I've somehow misinstalled the QEMU/ARM environment?
<br>I am trying to use scratchbox <a href="http://0.9.8.6">0.9.8.6</a>. Does Maemo 1.1 work with this version?<br><br>Any thoughts?<br><br>-- Cayle<br><br> <br><br><br>