>> what is your plan for dvk project? 1. Dependencies For time being, I plan to continue working on the scripts and identify if more dependencies can be removed. There are a few source code folders which I think can be removed.
2. Kernel Dependencies I have also attempted to isolate the android related kernel changes to only those that Dalvik needs at build/run-time. The .config files in the tar/dvkpatch folder have that. I want to streamline that further. 3. GIT Update Currently, once you have got the sources from GIT, there is no command in "idvk.sh" to update the sources with the latest from the GIT repository. That support needs to be added. 4. ARM generic product files and integration with emulator The x86 version creates an installer.img similar to the one created by eee_701 folks on this group and everything can be tested in a virtual machine. Similar support can be added for ARM (integration with emulator) so that the examples can be tested more easily. >> i success build some java test on dvk . for example , transform dom4j.jar >> to dex jar ,and use it to parse xml string . hehe Have you completed the testing..? If yes (!) you can add it to the dvkpatch/samples for reference of others. I will setup the SVN trunk with the code and provide you access. >> i debug dalvik in gdb insight , which a gui gdb tools . >> now ,i read the dalvik source code . i think if it possible put dalvik to >> j2ee . ( google app engine may use dalvik .) Debugging with Insight might be helpful to readers. You might want to start off by adding a Wiki page on the project with How-to instructions! --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
