diff options
author | Steve Slaven <bpk@hoopajoo.net> | 2011-12-13 16:44:31 (GMT) |
---|---|---|
committer | Steve Slaven <bpk@hoopajoo.net> | 2011-12-13 16:44:31 (GMT) |
commit | 42b0ad635034b4f663055f7dec9088fc94820b1e (patch) | |
tree | 7c11190f01c78c67ed815fd2ab4b115f030f09ad /README | |
download | RemoteContext-42b0ad635034b4f663055f7dec9088fc94820b1e.zip RemoteContext-42b0ad635034b4f663055f7dec9088fc94820b1e.tar.gz RemoteContext-42b0ad635034b4f663055f7dec9088fc94820b1e.tar.bz2 |
Diffstat (limited to 'README')
-rw-r--r-- | README | 27 |
1 files changed, 27 insertions, 0 deletions
@@ -0,0 +1,27 @@ +To set up the project: + +Go to properties -> add external jar -> path to android/platforms/4/android.jar + + +To create the jar: + +Right-click the RootContext.java in eclipse -> export -> jar + +This will exclude the stub files needed to compile, creating a normal java +jar, then you need to make it a dex jar: + +dx --dex --outfile output.jar RootContext.jar + +Include the output.jar file for the app_process jar + +This jar needs to be dx'ed so it will run from android, normally if you +include a jar in your project and build an apk it will be dx'ed when it is +put in the apk. Since we use this as an asset and spool it out to run +natively we must dx it ourself. + +The dx tool can also create a jar from a single .class file, so if you +compiled using a command line tool you can just create the jar from the +.class: + +dx --dex --output=RemoteContext.jar net/hoopajoo/android/RemoteContext.class + |