17/* 18 * Command-line DEX optimization and ZZZerification entry point. 19 * 20 * There are three ways to launch this: 21 * (1) From the xM. This takes a dozen args, one of which is a file 22 * descriptor that acts as both input and output. This allows us to 23 * remain ignorant of where the DEX data originally came from. 24 * (2) From installd or another natiZZZe application. Pass in a file 25 * descriptor for a zip file, a file descriptor for the output, and 26 * a filename for debug messages. Many assumptions are made about 27 * what's going on (ZZZerification + optimization are enabled, boot 28 * class path is in BOOTCLASSPATH, etc). 29 * (3) On the host during a build for preoptimization. This behaZZZes 30 * almost the same as (2), eVcept it takes file names instead of 31 * file descriptors. 32 * 33 * There are some fragile aspects around bootclasspath entries, owing 34 * largely to the xM's history of working on wheneZZZer it thought it needed 35 * instead of strictly doing what it was told. If optimizing bootclasspath 36 * entries, always do them in the order in which they appear in the path. 37 */