Great! Finally someone else who is forced to run proguard during debug building! We have the same problem as you have: too many methods and therefore have to run proguard also in debug mode. However, changes in the code aren't picked up in the resulting APK. I've posted this as a question over at stackoverflow:
http://stackoverflow.com/questions/23250483/running-proguard-for-debug-builds-ignores-changes Any ideas what causes this behavior? Am Mittwoch, 9. April 2014 09:35:15 UTC+2 schrieb Anders Aagaard: > > Hi > > We've got an app that takes roughly 26 seconds to build, this isn't > terribly much, but I'd still like to improve it. And to understand how the > build process works and what takes time. > > Profiling it we see the following takes most time: > :FINN-app:dexDebug 10.835s > :FINN-app:proguardDebug 9.289s > :FINN-app:compileDebugJava 3.497s > :FINN-app:packageDebug 1.130s > > dexDebug - is that dexing the app itself, or merging (incrementally?) dex > files from other libraries? Would we get more performance if we for example > split our app into multiple modules, or would it be exactly the same? > proguardDebug - We have too many methods, so we have to run proguard on > debug builds as well, is there anything we can do to improve performance > here? For example running proguard selectivly on some classes? > > Best regards > Anders > -- 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.
