We're doing this : https://gist.github.com/andaag/80892292638e02159fb1 - same thing but built on the aar's. Then we publish that to our internal maven repo and use it through gradle.
Note that if you use the gradle approach it'll pickup the artifact as changed every time, and redex it on every build. Considerably slowing down the build times :/ On Tue, Oct 7, 2014 at 10:02 AM, Tomáš Procházka <[email protected]> wrote: > And what about something like this > https://gist.github.com/dmarcato/d7c91b94214acd936e42 > But I hope, that Google Play Services will be separated to multiple > libraries directly by Google. > > > Dne pátek, 26. září 2014 9:54:48 UTC+2 Anders Aagaard napsal(a): > >> Hi >> >> Running proguard on every build (due to max method count) is a bit slow. >> Is there any way we can speed it up by for example saying "we dont use >> analytics, we can filter out package com.google.analytics." and just delete >> that without scanning dependencies/usages? >> >> Right now we use 30 seconds to build on our work laptops, 10 of that is >> proguard. I figure with an approach like this the proguard part of it >> wouldn't take any time at all. >> >> Best regards >> Anders >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "adt-dev" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/adt-dev/T3mO0xGB50k/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Mvh Anders Aagaard -- 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.
