Thanks Xavier for a great implementation, looks like NDK support is heading in the right direction!
I used your examples to compile an NDK library I have with no issues. However, one feature request, when you can, is to either allow me to override (or merge) the Android.mk file with my own so that I can fully customize the NDK build, or provide additional library/path linking options. I need to add "-Wl,-whole-archive path/to/static/lib -wl,-no-whole-archive" to my NDK library as well as link a prebuilt .so library against my NDK library. I have a custom built arm library for Python (libpython.so) that my NDK code requires linking against, but I don't see an "easy" way to provide a path (-L) for it. As a work around, I am tagging on to the end of the first ldLibs entry as such in the mean time: ldLibs "log -lpython -L/Users/my_build/libs/ -wl,-no-whole-archive /Users/my_build/libs/libxml2.a" I love Android Studio and look forward to full NDK support, thanks for the hard work, it's working quite well already! On Thursday, December 26, 2013 7:39:45 PM UTC-6, Xavier Ducrohet wrote: > > Version 0.7.2 was published on MavenCentral. > > You can put your prebuilts in src/main/jniLibs/... > There's a sample called ndkJniLib that shows the expected folder structure > in there. > > -- > 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/groups/opt_out.
