elate could care less about your manifest, you have to supply the name of the class to execute on the command line to it.
Here's my test, a slide show program that sucks images out of a ZIP file. It invokes the e-ink updates e.g. its "ported" to the iLiad.
To compile:
javac -classpath irex.jar -source 1.3 -target 1.1 Test1.java
To Jar:
jar cf Test1.jar Test1*.class
To run it I use this shell script:
Code:
#!/bin/sh
EXECPATH=sys/platform/linux/taoref/er10xx
IMGPATH=$EXECPATH
export DISPLAY=:0
export ELATE_FB_TTY=/dev/tty0
#export ELATE_KTRACE=/tmp/ktrace.log
export ELATE_DEBUGSTUB=7990
cd /home/intent/
if [ ! -d /home/intent/ROOTDIR ]
then
ln -s / ROOTDIR
fi
JVMARGS="-v -classpath $1;MobipocketCoreReader.jar;kxml2-2.3.0.jar;irex.jar
OPTIONS="-capp/stdio/jcode $JVMARGS"
exec $EXECPATH/elate -B $IMGPATH/target.img -g2 -l $EXECPATH "$OPTIONS"
java.sh Test1.jar Test1 ROOTDIR/path/to/file.zip
The elate can't see file's that begin with /, you have to use the ROOTDIR symlink to get to them.
Tap the screen to exit the program.
The -v lets you see the classes load, important for sussing out why elate is having heart burn over your code.
The commented out ktrace lets System.out go to the console.