How and what converts the Java bytecode to Android dex files?

Question

How and what exactly converts the java byte-code to dex file in Android ?

I know that the only part Android people have done to save them from licensing issues, making the system fast for execution, low memory need and other more features as it is register based VM.

But what name I can tell to the part it doing so?

Answer 1

Go through bellow url and read all details Detail URL

The general process for a typical build is outlined below:

1. The Android Asset Packaging Tool (aapt) takes your application resource files, such as the AndroidManifest.xml file and the XML files for your Activities, and compiles them. An R.java is also produced so you can reference your resources from your Java code.

2. The aidl tool converts any .aidl interfaces that you have into Java interfaces.

3. All of your Java code, including the R.java and .aidl files, are compiled by the Java compiler and .class files are output.

4. The dex tool converts the .class files to Dalvik byte code. Any 3rd party libraries and .class files that you have included in your project are also converted into .dex files so that they can be packaged into the final .apk file.

5. All non-compiled resources (such as images), compiled resources, and the .dex files are sent to the apkbuilder tool to be packaged into an .apk file.

6. Once the .apk is built, it must be signed with either a debug or release key before it can be installed to a device.
7. Finally, if the application is being signed in release mode, you must align the .apk with the zipalign tool. Aligning the final .apk decreases memory usage when the application is running on a device.