Hi,
as we all know, Gradle Android plugin now supports native builds in a new
manner, by using ndk{} DSL in build.gradle. No more calling ndk-build
manually - that's great!
It seems like a very powerful solution and a good direction of developing
NDK support in Gradle since we can reconfigure NDK builds in our variants
(buildTypes/flavors).
Unfortunately, I have a project which has quite sophisticated Android.mk
and Application.mk files. I'm doing my best to leave them and switch to the
generated one to have above feature, but here is my first blocker.
My native code is shared between Android and iOS application, so I have my
native sources not only in src/main/jni but also in other locations.
Therefore, my Android.mk have something like:
LOCAL_SRC_FILES := \
SwigBindings.cpp \
../../src/platforms/android/platform.cpp \
../../src/accounts/accountDetails.cpp \
../../src/accounts/accountHistory.cpp \
[...]
LOCAL_C_INCLUDES := \
$(LOCAL_PATH)/../../include \
$(LOCAL_PATH)/../../src \
$(LOCAL_PATH)/../../src/http \
[...]
The questions is - is there any way to generate Android.mk with
LOCAL_SRC_FILES and LOCAL_C_INCLUDES containing not only sources from
src/main/jni but also from other locations?
I looked over the web and found only simple samples which are not suitable
for me, e.x. ndkSanAngeles in gradle-samples-0.10,
or http://dbro.pro/blog/2014/01/04/gradle-ndk.html.
Does Gradle Android plugin have that feature, is it documented somewhere?
M.
--
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.
