Thanks for the advice James. I think we are going to do something similar to your suggestion since our architecture is already modularized.
On Friday, July 25, 2014 2:26:23 AM UTC-7, James Wald wrote: > > Due to the fact that Amazon's SDK is not the Android SDK I wouldn't try to > bundle them together into a single project. They really are separate > products. You might be better off if you create reusable Android library > projects that contain all of the components that work across both products. > You could then add those libraries as dependencies to two separate > top-level projects. One for Android (i.e. Google) and another for Amazon. > > On Wednesday, July 23, 2014 9:05:10 AM UTC-10, [email protected] > wrote: >> >> Hi, our current product uses productFlavors to support an array of >> devices. However, the new Fire Phone has a custom SDK used to compile. >> Thus, we have to adjust the compileSdkVersion and the targetSdkVersion. >> After reading previous posts, I've found that dynamically setting the >> compileSdkVersion based on a flavor >> <https://groups.google.com/forum/#!searchin/adt-dev/compileSdkVersion$20productFlavors/adt-dev/D0bhkcKsSKk/4VKcBXSiD_AJ> >> >> doesn't seem like an option. Is there a work around that can be done in the >> build.gradle or will this need to be done outside of gradle? >> > -- 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.
