That was it.
I switched off Shared Runtime in the GUI, but it was placed in the wrong
XML-Element. (By xamarin? by VS?)
No works fine.
Thanks.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/4-2-5-always-packs-x86-tp5711149p5711165.html
Sent from the Mono for An
On Aug 3, 2012, at 10:44 AM, tsukrov 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):
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?
optimize = true,
DEBUG, TRACE - off
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/4-2-
Debug or Release builds?
Release builds shouldn't be embedding x86 by default; at least, they don't for
me. Debug builds will, so that new projects will easily deploy to the x86
emulator without needing to update the project first.
- Jon
___
Monodro
Subj.
No matter, what project settings are.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/4-2-5-always-packs-x86-tp5711149.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid mailing