Matt, Don't know if it helps, my msbuild goes like:
.... ComponentBuild (libraries); CopyComponentFiles (copy files somewhere else); XenocodeComponent (obfuscate libraries); ExeBuild (build main app, just a stub really - calls UpdateAndroidResources and SignAndroidPackage); SignAndAlign (jar signer and zipalign) ... Cheers, Andy -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Matt Sent: 27 April 2012 17:10 To: [email protected] Subject: Re: [mono-android] Linking problem with obfuscated assembly Andy , Thanks for your help. The obfuscator that I am using (9-rays) has an option to emit alphabetic type names, which I would assume are all valid Java names. I tried using this option and it didn't help. Do you know of any way to get more useful debug information from the M4A linker? Based on the error that I get, it's very difficult to determine the root cause of the problem. I would also be interested in how your build process is working. As I mentioned, when I call the SignAndroidPackage msbuild target, my main application assembly is regenerated, overwriting the obfuscated assembly. Thanks, Matt -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/Linking-problem-with-obfuscate d-assembly-tp5666519p5670720.html Sent from the Mono for Android mailing list archive at Nabble.com. _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
