The new release do contain the fix. It now look for Application.mk in the
same folder as the Android.mk. We added an arguments options to the
configuration. For example.
android {
defaultConfig {
ndkBuild {
arguments "APP_PROJECT_PATH=/some/other/directory"
}
}
}
On Thursday, June 9, 2016 at 9:06:14 AM UTC-7, Iliya wrote:
>
> I just saw the new version released today is this the version with the fix
> in place. Also is there any documentation on how to define compile flags or
> point to a custom Application.mk?
>
> On Thursday, 26 May 2016 12:20:55 UTC-5, Raymond Chiu wrote:
>>
>> This is a known issue and will be fixed in the next version. Sorry for
>> the trouble.
>>
>> Raymond
>>
>> On Friday, May 20, 2016 at 2:15:14 PM UTC-7, Streets Of Boston wrote:
>>>
>>> Hi,
>>>
>>> I have a project that currently uses a custom task to execute an
>>> NDK-build. I upgraded to A.S. 2.2 and I can now remove that custom task and
>>> my sources build.
>>> However, there are some issues
>>>
>>>
>>> I build again API-level 23, use the latest gradle-plugin version and
>>> have these snippets in my build.gradle (it is a library-module):
>>>
>>> defaultConfig {
>>>
>>> ...
>>>
>>> ndk {
>>> moduleName "MCInterface"
>>> cFlags "-D_____default_config_ndk_____"
>>> }
>>>
>>> ndkBuild {
>>> cFlags "-D_____default_config_ndkBuild_____"
>>> cppFlags "-D_____default_config_ndkBuild_____"
>>> }
>>>
>>>
>>> ...
>>>
>>> }
>>>
>>>
>>>
>>> externalNativeBuild {
>>> ndkBuild {
>>> path file("src/main/jni/Android.mk")
>>> cFlags += "-D__WITH_DTLS__ -D_____externalNativeBuild_____"
>>> cppFlags "-D_____externalNativeBuild_____"
>>> }
>>> }
>>>
>>>
>>>
>>> - When running the build, the value of the '*path*' property doesn't
>>> matter; it is not used at all.
>>> It seems the NDK_PROJECT_PATH is *always*
>>> "<module-root>/src/main/jni/Android.mk" and disregards the value as
>>> configured in the build.gradle.
>>> Leaving out the 'path' property however, will give an error.
>>> - 'cFlags' and 'cppFlags' properties are not used at all. They always
>>> default to some default set of values when running ndk-build.
>>> I tried setting them at various levels in the build.gradle, but to no
>>> avail.
>>> - There is no way to make the ndk-build use an Application.mk file at
>>> all. It is ignored.
>>>
>>> How can I use a specific Android.mk and/or Application.mk file?
>>> If the Application.mk file is ignored, how can I tell the ndk-build to use
>>> or override certain compile and link flags/options app-wide?
>>>
>>> Thanks,
>>> --- Anton.
>>>
>>>
--
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 adt-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
