Bug 3069 - Bindings projects are broken in eval installations
Summary: Bindings projects are broken in eval installations
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 5.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-01-25 17:33 UTC by Adam Kemp
Modified: 2012-01-25 18:42 UTC (History)
1 user (show)

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:

Description Adam Kemp 2012-01-25 17:33:33 UTC
Every once in a while we have a new developer start with just an eval version of MonoTouch because we don't yet have a license for him. Unfortunately, the bindings projects we created will not build for those developers. They are just broken in an eval installation.

To reproduce, download and install the evaluation version of MonoTouch and then try to build any ObjectiveC bindings project.

Our only workaround is to manually edit the solution/projects for these users and replace the bindings projects with generic projects that have custom build commands that run btouch.
Comment 1 Jeffrey Stedfast 2012-01-25 18:42:43 UTC
Fixed in git master - fwiw, you could just copy the /Library/Frameworks/Mono.framework/External/xbuild* dirs.

The post-install script for the eval version didn't get synced up with the commercial version and so those directory trees weren't being created.