On Aug 2, 7:07 am, profect <[email protected]> wrote: > Dexopt can deal with two kinds of files, zip and dex, which are > differentiated by command line options, --zip and --dex. I find one entry > point for --dex in Android system code. It is in the function > dvmOptimizeDexFile() in the file DexOptimize.c. In this function only dex is > specified. My questions are: > > 1. Where are the entry points for zip files? I know there are cases that zip > files are optimized, but I didn't find where they are. > 2. Is there any other entry point for dex file optimization in the existing > code?
I'm not sure what you mean by "entry point". The higher-level design is discussed in dalvik/docs/dexopt.html: http://android.git.kernel.org/?p=platform/dalvik.git;a=blob_plain;f=docs/dexopt.html;hb=HEAD In the "Preparation" section, three ways to initiate DEX optimization are listed (VM "just in time", system installer, build system). If you haven't found dalvik/vm/JarFile.c, I'd recommend looking through that. The files are locked with flock() while optimization is in progress. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
