Multi-dex is a complicated process that is not currently incremental. On Mon, May 4, 2015 at 8:27 PM, wsgfz Deng <[email protected]> wrote:
> I just simply delete one line of my main project's java file,and it took > me more than 1 minute to get the apk. Same with the Android Studio. > here is the gradle log of the main project: > > :mainProject 1m7.88s (total) > :mainProject:dexDebug 44.924s > :mainProject:shrinkDebugMultiDexComponents 8.432s > :mainProject:packageDebug 5.268s > :mainProject:packageAllDebugClassesForMultiDex 3.529s > :mainProject:createDebugMainDexClassList 2.990s > :mainProject:compileDebugJava 2.197s > :mainProject:zipalignDebug 0.190s > > It seems that the dexDebug task took the most of the time. Any suggestions > to improve this? > > PS. > Besides the main project, we have other 9 library projects as gradle > module which are compiled with the main project.BUT they are all up-to-date. > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
