Bug 7904 - MonoDevelop chooses Mono's compiler instead of MonoTouch's when compiling an iOS project using Mono 2.11.5
Summary: MonoDevelop chooses Mono's compiler instead of MonoTouch's when compiling an ...
Status: RESOLVED INVALID
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2012-10-18 17:34 UTC by PJ
Modified: 2012-10-25 17:45 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED INVALID

Description PJ 2012-10-18 17:34:37 UTC
Here is a gist of the same project being compiled where the only difference is the mono: https://gist.github.com/a105a17ccffdac7c92af

As you can see, the output from the build with 2.11.5 shows that mcs from the mono framework is being used. For 2.10.9, MonoDevelop (correctly) chooses the smcs contained within MonoTouch. 


Mono 2.10.9_11 (stable)

Mono 2.11.5_0 e0b5cc1b8f7389eaaa2fab67572d0cd0c09497c2



Other version info:

MonoDevelop 3.0.5
Installation UUID: b5aed0d2-0f63-4725-91ca-eb558d43bdf2
Runtime:
	Mono 2.11.5 (master/e0b5cc1)
	GTK 2.24.11
	GTK# (2.12.0.0)
	Package version: 211050000
Apple Developer Tools:
	 Xcode 4.5 (1839)
	 Build 4G182
Mono for Android: 4.2.8
Android SDK: /Users/xamarinqa/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		2.1 (API level 7)
		2.2 (API level 8)
		2.3 (API level 10)
		3.1 (API level 12)
		4.0 (API level 14)
Java SDK: /usr
Monotouch: 6.0.5
Build information:
	Release ID: 30005000
	Git revision: c01e9f4183da852b14fc73d8103172e5955bfc7c
	Build date: 2012-10-17 23:27:27+0000
	Xamarin addins: cac5ab115646ddb66d38edf93dbb88ef004c5f8f
Operating System:
	Mac OS X 10.7.4
	Darwin dynamic-095.bos.xamarin.com 11.4.0 Darwin Kernel Version 11.4.0
	    Mon Apr  9 19:32:15 PDT 2012
	    root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-10-18 18:31:53 UTC
One fix/workaround is to change the default runtime to 2.10.10, here: http://screencast.com/t/EnDoDCncO7
Comment 2 Jeffrey Stedfast 2012-10-25 17:33:15 UTC
apparently this shouldn't be a problem.

Let me know if it causes any compile errors, though.
Comment 3 Mikayla Hutchinson [MSFT] 2012-10-25 17:45:17 UTC
Note: Mono's improved C# compiler in 2.11+ is capable of targeting any framework profile - it no longer needs a custom build of the compiler for each profile. Since we're passing the MonoTouch mscorlib to it, it should build correctly. When MonoTouch depends on Mono 3.0, its smc will likely become a symlink to the system mcs.