Gradle has to do things a bit differently due to variants and in order to provide more flexilibty, so yes right now it copies things around too much, but this should be less an issue in incremental builds. We do intend to fix this but it's pending on a change in Gradle.
Can you tell me which task tasks the longest? Maybe send me the output of --profile? On Fri, Sep 25, 2015 at 2:02 AM, Zsolt Bertalan <[email protected]> wrote: > We are moving a fairly big project from Eclipse to Android Studio. The > project has a deep dependency structure with a framework library project > and an app with lots of library modules. The build times for the app > project are more than 8 minutes compared to less than one minute in > Eclipse. I noticed that this is mainly because we have a library with all > the resources and Gradle copies these resources everywhere to every > dependent module. My guess is that Eclipse uses only links for that kind of > dependency. > > Is there a switch in AS/Gradle for similar behavior? Or is something > planned to rectify this issue? Or should we completely refactor our project? > > -- > 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.
