Thank you Thasso, that really helped!
On Thursday, November 12, 2015 at 3:25:11 PM UTC+6, Thasso Griebel wrote:
>
> Hi Igor,
>
> one thing that you can try to work around this is to manipulate the final
> list of arguments in the link task after it was created:
>
> tasks.whenTaskAdded { t ->
> // find the tasks that links the final shared library
> if(t.name ==~ /link.*Shared.*/){
> println "${t.linkerArgs}"
> }
> }
>
> Best,
> -Thasso
>
>
> On Tuesday, November 10, 2015 at 6:29:25 PM UTC+1, Igor Eremeev wrote:
>>
>> Hey guys,
>>
>> I'm trying to build some native code with
>> gradle-experimental:0.3.0-alpha7 plugin, and I encountered a problem with
>> link flags, which are added automatically by the plugin.
>>
>> Long story short, I need to put some .a dependency before -lc++_static to
>> override a symbol, but the plugin always puts its flags on the top.
>>
>> Tried doing some magic with components.android {binaries.afterEach
>> {it.mergedNdkConfig}} bit this list seems to be empty, and only works for
>> adding new flags.
>>
>> Is there some way to access final list of flags to manually edit them? Or
>> maybe some way to fully prohibit plugin from adding default flags?
>>
>>
--
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.
