The best thing would be for them to create an aar with all the .so (in all ABI variants). Then you can just depend on it through the 'compile' configuration (no need to use runtime, which is called apk for us BTW, since 'compile' dependencies are also added to the APK).
On Thu, Jan 22, 2015 at 2:55 AM, Eyal Gal <[email protected]> wrote: > we have just moved to gradle and we have a project in which the .so comes > from another team in a different location, so they have an artifactory > server which is defined in our build.gradle. > I'm now sure how the other team should upload their .so files and how i > should define them, i mean: > 1. should they upload .so or wrap the .so in a jar ? > 2. should i define the dependency as 'compile' only or 'compile' AND > 'runtime' since it's an .so file.. > 3. will android gradle plugin know to take the dependecy and place it in > the right place so the android app will be able to find it ? > > -- > 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.
