Bug 11218 - Merging Mono Runtime into app bundle
Summary: Merging Mono Runtime into app bundle
Status: RESOLVED NORESPONSE
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: mmp ()
Version: 1.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Sebastien Pouliot
URL:
Depends on:
Blocks:
 
Reported: 2013-03-17 23:04 UTC by andy_wu
Modified: 2013-05-28 12:38 UTC (History)
2 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 NORESPONSE

Comment 1 Sebastien Pouliot 2013-03-18 14:34:50 UTC
Do you have Xcode installed ?

If so can you check if you have the "Command-Line Tools" installed ? (it's an additional download you need to do from inside Xcode preferences)*

Otherwise please do a build with "-v -v -v" added to your project options and also include all the product versions from Xamarin Studio's about box.


* the upcoming Xamarin.Mac 1.2 won't require the "Command-Line Tools" but they are often useful to have anyway (e.g. for iOS development).
Comment 2 Aaron Bockover [MSFT] 2013-05-28 12:38:41 UTC
Closing due to no response. Xamarin 1.2 was released already and should have fixed this issue. Please re-open if the issue is still valid.