On Aug 3, 2012, at 10:44 AM, tsukrov <[email protected]> wrote:
> That explains it! Release is fine.
>
> It's a custom configuration, that makes problems. ReleaseOBF or something
> like that.
>
> How can I check if it's considered debug or release?
See Novell.MonoDroid.Common.targets (abbreviated):
<PropertyGroup>
<AndroidUseSharedRuntime
Condition="'$(AndroidUseSharedRuntime)' == ''">true</AndroidUseSharedRuntime>
<AndroidSupportedAbis Condition="'$(AndroidSupportedAbis)' ==
''">armeabi</AndroidSupportedAbis>
<!-- If the user is using the shared runtime, we are going to
partially override their supported Abis and support x86 as well -->
<AndroidSupportedAbis
Condition="'$(AndroidUseSharedRuntime)'">$(AndroidSupportedAbis);x86</AndroidSupportedAbis>
</PropertyGroup>
Adding x86 is determined by the $(AndroidUseSharedRuntime) MSBuild property,
which in turn is set in your .csproj. When it's False (the default for Release
builds), x86 isn't added (and $(AndroidSupportedAbis) is used). If it's True
(which is also the default value if $(AndroidUseSharedRuntime) isn't
specified!), then x86 is added.
The fix for your ReleaseOBF configuration is to ensure that it sets
$(AndroidUseSharedRuntime) to False:
<PropertyGroup Condition=" '$(Configuration)' == 'ReleaseOBF' ">
<AndroidUseSharedRuntime>False</AndroidUseSharedRuntime>
</PropertyGroup>
- Jon
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
