dex - What is Android Pre-Dexing and how to does it increase performance? -


i see ant script of android has message "pre-dexing". dex , pre-dex uses same options, except in 1 case 1 jar @ time, in other case multiple jars @ time.

what real need? pre-dex mandatory?

e.g

the ' characters around executable , arguments not part of command.       [dex] pre-dexing f:\users\tejasoft\work\fnd\cmn\tools\social\sz\demo\libs\pinit-sdk-1.0.jar -> pinit-sdk-1.0-e3bebafa2727504605edf3d8d85b5d46.jar        [dx] current os windows 7        [dx] executing 'd:\apps\java\embd\cmn\android\oems\google\adt\4.x\4.3.x\4.3\sdk\build-tools\18.1.0\dx.bat' arguments:        [dx] '--dex'        [dx] '--output'        [dx] 'f:\users\tejasoft\work\fnd\cmn\tools\social\sz\demo\bin\dexedlibs\pinit-sdk-1.0-e3bebafa2727504605edf3d8d85b5d46.jar'        [dx] 'f:\users\tejasoft\work\fnd\cmn\tools\social\sz\demo\libs\pinit-sdk-1.0.jar'        [dx]         [dx] ' characters around executable , arguments        [dx] not part of command. execute:java13commandlauncher: executing 'd:\apps\java\embd\cmn\android\oems\google\adt\4.x\4.3.x\4.3\sdk\build-tools\18.1.0\dx.bat' arguments: '--dex' '--output' 'f:\users\tejasoft\work\fnd\cmn\tools\social\sz\demo\bin\dexedlibs\pinit-sdk-1.0-e3bebafa2727504605edf3d8d85b5d46.jar' 'f:\users\tejasoft\work\fnd\cmn\tools\social\sz\demo\libs\pinit-sdk-1.0.jar'  ' characters around executable , arguments not part of command.       [dex] converting compiled files , external libraries f:\users\tejasoft\work\fnd\cmn\tools\social\sz\demo\bin\classes.dex...        [dx] current os windows 7        [dx] executing 'd:\apps\java\embd\cmn\android\oems\google\adt\4.x\4.3.x\4.3\sdk\build-tools\18.1.0\dx.bat' arguments:        [dx] '--dex'        [dx] '--output'        [dx] 'f:\users\tejasoft\work\fnd\cmn\tools\social\sz\demo\bin\classes.dex'        [dx] 'f:\users\tejasoft\work\fnd\cmn\tools\social\sz\demo\bin\classes'        [dx] 'f:\users\tejasoft\work\fnd\cmn\tools\social\sz\demo\bin\dexedlibs\classes-144740ee5cf8b90b747300d19fb8201e.jar'        [dx] 'f:\users\tejasoft\work\fnd\cmn\tools\social\sz\demo\bin\dexedlibs\classes-1593da1bb60c5ec741aca494963e04a3.jar'        [dx] 'f:\users\tejasoft\work\fnd\cmn\tools\social\sz\demo\bin\dexedlibs\classes-37bb5269e4fbd6dda9900fea95c0c29b.jar' 

it's useful remember in case working in java, not same thing dalvik runtime. java, oracle, uses different virtual machine, while dalvik fine-tuned mobile devices.

the dex processes take java compiled jar files , converts them dalvik executable files (.dex) files run on android. oracle jvm uses different bytecode dalvik runtime, making step necessity.

there process libraries might have included in project, compiled standard java compiler, , process actual project.

it's done in 2 steps final process, application, requires access dexed library files avoid having references code change while process busy.

you can find out more @ http://source.android.com/devices/tech/dalvik/index.html - see dalvik scheduled replacement called art.


Comments

Popular posts from this blog

c++ - CryptStringToBinary API behavior -

java.util.scanner - How to read and add only numbers to array from a text file -

iphone - Three second countdown in cocos2d -