Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
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.
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.