The experimental plugin do not use ndk-build. Instead it invokes the compiler directly. You can get additional information by adding --info to your gradle command.
The plugin sets a number of flags by default, similar to ndk-build. I will check on the -finline-functions flag. On Wednesday, December 16, 2015 at 10:47:24 AM UTC-8, [email protected] wrote: > > As a side note, I get the following warning (I treat warnings as errors) > However, I have not been able to determine where it gets added to the > build process and I'm not adding it in my app's gradle.build > android.ndk.with{} block. > > clang++: error: optimization flag '-finline-functions' is not supported > > On Wednesday, December 16, 2015 at 10:41:12 AM UTC-8, [email protected] > wrote: >> >> Greetings, >> >> I'd like to pass in extra options to the ndk-build command. >> In particular, "V=1" and "NDK_LOG=1" to view the raw compiler linker >> calls made by ndk-build. >> >> A) >> How do we inject additional command line options to the ADT's ndk-build >> command? >> >> I switched to the experimental plugin (versus calling ndk-build -C >> myself). >> >> Alternatively, I suppose I could revert to using "ndk-build -C xxx" tasks >> with my own hand-crafted Android.mk make files in order to have this >> fine-toothed control. >> >> However, I'm trying to stay with the experimental plugin because it is >> the way of the future. >> (And so many gradle.build syntax changes related to using the >> experimental plugin.) >> >> B) >> Environment: >> - OSX 10.10 (Yosemite) >> - AS v1.5 (stable channel) >> - gradle-2.6 >> - gradle-experimental:0.3.0-alpha5 >> >> >> >> 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.
