Bug 22366 - IBTool / MMPTask errors when /Applications/Xcode.app doesn't exist or xcode-select -p is set to /Applications/Xcode6-Beta6.app/
Summary: IBTool / MMPTask errors when /Applications/Xcode.app doesn't exist or xcode-s...
Status: RESOLVED FIXED
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Release Readiness ()
Version: 1.10.0
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Chris Hamons
URL:
Depends on:
Blocks:
 
Reported: 2014-08-26 13:32 UTC by troy-dawson
Modified: 2014-08-28 12:31 UTC (History)
9 users (show)

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


Attachments
Build error (111.87 KB, text/plain)
2014-08-26 15:44 UTC, troy-dawson
Details
Unified project template build error (7.25 KB, text/plain)
2014-08-27 17:46 UTC, troy-dawson
Details


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 FIXED

Description troy-dawson 2014-08-26 13:32:24 UTC
Can't build any Unified project on 10.10 DP6 / Xcode 6 Beta 6, from the empty template Xamarin.mac projects to SceneKit WWDC 2014 demo at http://developer.xamarin.com/samples/SceneKitSessionWWDC2014/

Compile error for the latter:


Building Solution: Scene Kit Session WWDC 2014 (Debug)

Building: Scene Kit Session WWDC 2014 (Debug)

Build started 8/26/2014 10:31:47 AM.
__________________________________________________
Project "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/Scene Kit Session WWDC 2014.csproj" (Build target(s)):
	
	Target _CoreCompileInterfaceDefinitions:
		Tool /usr/bin/ibtool execution started with arguments: --errors --warnings --notices --output-format xml1 --compile "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/obj/Debug/ibtool/MainMenu.nib" "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/MainMenu.xib"
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Mac/Xamarin.Mac.Common.targets: error : Failed to load output manifest for ibtool: Unrecognized property list format.
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Mac/Xamarin.Mac.Common.targets: error : Output manifest contents: 
	Task "IBToolTask" execution -- FAILED
	Done building target "_CoreCompileInterfaceDefinitions" in project "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/Scene Kit Session WWDC 2014.csproj".-- FAILED
	
Done building project "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/Scene Kit Session WWDC 2014.csproj".-- FAILED

Build FAILED.
Errors:

/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/Scene Kit Session WWDC 2014.csproj (Build) ->
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Mac/Xamarin.Mac.Common.targets (_CoreCompileInterfaceDefinitions target) ->

	/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Mac/Xamarin.Mac.Common.targets: error : Failed to load output manifest for ibtool: Unrecognized property list format.
	/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Mac/Xamarin.Mac.Common.targets: error : Output manifest contents: 

	 0 Warning(s)
	 2 Error(s)

Time Elapsed 00:00:00.2888640

---------------------- Done ----------------------

Build: 2 errors, 0 warnings
Comment 1 Chris Hamons 2014-08-26 14:41:47 UTC
Could you paste the results from the following commands:

xcode-select -p

/usr/bin/ibtool --errors
--warnings --notices --output-format xml1 --compile
"/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/obj/Debug/ibtool/MainMenu.nib"

 /usr/bin/ibtool --version
Comment 2 troy-dawson 2014-08-26 14:50:58 UTC
Troys-MacBook-Pro:~ troy$ xcode-select -p
/Library/Developer/CommandLineTools

Troys-MacBook-Pro:~ troy$ /usr/bin/ibtool --errors --warnings --notices --output-format xml1 --compile "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/obj/Debug/ibtool/MainMenu.nib"
xcode-select: error: tool 'ibtool' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

Troys-MacBook-Pro:~ troy$ /usr/bin/ibtool --version
xcode-select: error: tool 'ibtool' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance


(I have indeed installed the "Late August 2014" 10.10 command line tools via Xcode's link to developer.apple.com)
Comment 3 Chris Hamons 2014-08-26 14:55:51 UTC
This is the problem - "/Library/Developer/CommandLineTools"

You need to set code-select to point to a real Xcode instance.

xcode-select -s /Applications/<Some Xcode you have installed>

Let me know if that fixes your issue.
Comment 4 troy-dawson 2014-08-26 14:59:17 UTC
yeah, Googling the error, via 

http://stackoverflow.com/questions/17980759/xcode-select-active-developer-directory-error-on-osx-mavericks

I did the following:

Troys-MacBook-Pro:~ troy$ sudo xcode-select -switch /Applications/Xcode6-Beta6.app/Contents/Developer/

The output of the requested ibtool commands now:

Troys-MacBook-Pro:~ troy$ /usr/bin/ibtool --version
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.ibtool.version</key>
	<dict>
		<key>bundle-version</key>
		<string>1878</string>
		<key>short-bundle-version</key>
		<string>6.0</string>
	</dict>
</dict>
</plist>
Troys-MacBook-Pro:~ troy$ /usr/bin/ibtool --errors --warnings --notices --output-format xml1 --compile "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/obj/Debug/ibtool/MainMenu.nib"
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.ibtool.errors</key>
	<array>
		<dict>
			<key>description</key>
			<string>Not enough arguments provided; where is the input document to operate on?</string>
		</dict>
	</array>
</dict>
</plist>

(buidling in XS still gives the same errors, too)
Comment 5 Chris Hamons 2014-08-26 15:11:19 UTC
So it looks like i cut off part of the command it is complaining about:

 Tool /usr/bin/ibtool execution started with arguments: --errors
--warnings --notices --output-format xml1 --compile
"/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/obj/Debug/ibtool/MainMenu.nib"
"/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/MainMenu.xib

Try

/usr/bin/ibtool --errors
--warnings --notices --output-format xml1 --compile
"/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/obj/Debug/ibtool/MainMenu.nib"
"/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/MainMenu.xib
Comment 6 troy-dawson 2014-08-26 15:24:57 UTC
Troys-MacBook-Pro:~ troy$ /usr/bin/ibtool --errors --warnings --notices --output-format xml1 --compile "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/obj/Debug/ibtool/MainMenu.nib" "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/MainMenu.xib"
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.ibtool.document.errors</key>
	<dict/>
	<key>com.apple.ibtool.document.notices</key>
	<dict/>
	<key>com.apple.ibtool.document.warnings</key>
	<dict/>
</dict>
</plist>
Comment 7 Chris Hamons 2014-08-26 15:26:27 UTC
That seems to have worked. Can you restart XS, rebuild, and post the errors now.
Comment 8 troy-dawson 2014-08-26 15:42:54 UTC
I've rebooted (briefly visited 10.9 partition then came back) and working on a fresh copy of the WWDC 2014 SceneKit project, am now getting this error:

MMPTASK: Error MM5306: Missing dependencies. Please install Xcode 'Command-Line Tools' component (MM5306)

This is the same error I was getting when I deleted the xibs from the template projects.

Attaching full build log in next comment.
Comment 9 troy-dawson 2014-08-26 15:44:15 UTC
Created attachment 7807 [details]
Build error
Comment 10 troy-dawson 2014-08-26 17:37:05 UTC
fwiw I to sanity check things I deleted the Xcode beta.app and reinstalled it, same error:

Build FAILED.
Errors:

/Users/troy/Downloads/SceneKitSessionWWDC2014-2/SceneKitSessionWWDC2014/Scene Kit Session WWDC 2014.csproj (Build) ->
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Mac/Xamarin.Mac.Common.targets (_CompileToNative target) ->

	MMPTASK: error MM5306: Missing dependencies. Please install Xcode 'Command-Line Tools' component

Reinstalling the 2014 Late August command line tools from Apple too, same error still.
Comment 11 troy-dawson 2014-08-27 09:59:26 UTC
I reinstalled my 10.10 system from scratch last night and am still blocked by this.

I verified I had a working Xcode Beta6 install first, had it install its internal tools (not the separate command line tools install, its own).

I took new Xamarin Mac Install from 1.2 -> 1.8, converting a new MonoMac project to XamMac and that built fine.

I upgraded 1.8 to 1.11.0.1 (Indie Edition) and converted the 1.8 empty XamMac project to Unified. XS requested I install ibtool and I allowed XS to launch the Apple CLI tools installer.

Getting this error on all Unified projects, including the 2014 SceneKit sample project:

/Users/troy/Projects/test1/test1/test1.csproj (Build) ->
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Mac/Xamarin.Mac.Common.targets (_CoreCompileInterfaceDefinitions target) ->

	/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Mac/Xamarin.Mac.Common.targets: error : Failed to load output manifest for ibtool: Unrecognized property list format.
	/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Mac/Xamarin.Mac.Common.targets: error : Output manifest contents: 
	/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Mac/Xamarin.Mac.Common.targets: error : Failed to load output manifest for ibtool: Unrecognized property list format.
	/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Mac/Xamarin.Mac.Common.targets: error : Output manifest contents: 


Running

Troys-MacBook-Pro:Projects troy$ /usr/bin/ibtool --errors --warnings --notices --output-format xml1 --compile "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/obj/Debug/ibtool/MainMenu.nib" "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/MainMenu.xib"

returned:

xcode-select: error: tool 'ibtool' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
Troys-MacBook-Pro:Projects troy$ 

so I did the xcode-select -switch to beta6 per above, verified ibtool worked in the terminal:


Troys-MacBook-Pro:Projects troy$ /usr/bin/ibtool --errors --warnings --notices --output-format xml1 --compile "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/obj/Debug/ibtool/MainMenu.nib" "/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/MainMenu.xib"
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.ibtool.document.errors</key>
	<dict/>
	<key>com.apple.ibtool.document.notices</key>
	<dict/>
	<key>com.apple.ibtool.document.warnings</key>
	<dict/>
</dict>
</plist>



restarted XS, and am still getting this compile error on my test projects.
Comment 12 Chris Hamons 2014-08-27 10:12:44 UTC
We have people internally who are seeing this as well. Investigating.
Comment 13 Mohit Kheterpal 2014-08-27 11:27:10 UTC
I have tried to reproduce this issue on OSX 10.10 and I am able to build and run Unified API Xamarin.mac template successfully without any error as shown in screencast : http://www.screencast.com/t/0te8CukL8

Environment info :
=== Xamarin Studio ===

Version 5.3 (build 435)
Installation UUID: 0b7eaebc-a0ed-4b58-81df-91e378cad28c
Runtime:
	Mono 3.8.0 ((no/62a857e)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 308000007

=== Apple Developer Tools ===

Xcode 6.0 (6256.16)
Build 6A280e

=== Xamarin.iOS ===

Version: 7.4.0.107 (Enterprise Edition)
Hash: 326547f
Branch: 
Build date: 2014-08-25 14:54:57-0400

=== Xamarin.Android ===

Version: 4.16.0 (Enterprise Edition)
Android SDK: /Users/Admin_Mac/Desktop/Anddk/android-sdk-macosx
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		3.2    (API level 13)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		4.5    (API level 21)
Java SDK: /usr
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)

=== Xamarin.Mac ===

Version: 1.10.0.10 (Enterprise Edition)

=== Build Information ===

Release ID: 503000435
Git revision: 1e0c5fa7482a0356a71dfa469a3f71f5478a4660
Build date: 2014-08-25 12:17:42-04
Xamarin addins: 69708b283b171ea053d0edfbf09d98457d21fbee

=== Operating System ===

Mac OS X 10.10.0
Darwin Admin-Macs-Mac-mini.local 14.0.0 Darwin Kernel Version 14.0.0
    Sat Aug  9 00:14:02 PDT 2014
    root:xnu-2782.1.80~2/RELEASE_X86_64 x86_64
Comment 14 troy-dawson 2014-08-27 11:40:39 UTC
My XS build is Version 5.3 (build 427) not 435

My Xamarin.Mac version is Version: 1.11.0.1 (Indie Edition) not 1.10.0.10
Comment 15 Chris Hamons 2014-08-27 16:59:23 UTC
So there is something strange going on. On my 10.10 box, running Xamarin.Mac 1.11.0.1 I'm building just fine.
Comment 16 Chris Hamons 2014-08-27 16:59:59 UTC
Can you go into XS preferences, Projects, SDK Locations, and tell me what your apple SDK location is set to?
Comment 17 troy-dawson 2014-08-27 17:06:02 UTC
This morning I downgraded to XamMac 1.8, but this setting hasn’t changed:

/Applications/Xcode6-Beta6.app

About XS / Details shows:

Apple Developer Tools
Xcode 6.0 (6256.16)
Build 6A280e
Comment 18 Chris Hamons 2014-08-27 17:09:31 UTC
That is the exact version I have. Looking to find a way to reproduce.
Comment 19 troy-dawson 2014-08-27 17:18:36 UTC
Upgrading from XamMac 1.8 to 1.11.0.1 (alpha channel), creating a new Unified project from the template, I've gotten a different error now.

/Users/troy/Projects/test7/test7/MMPTASK: Error MM9008: Building from the command-line requires a Business license. (MM9008) (test7)

The IDE log shows:

 Marker - Aug 27, 2014, 2:14:39 PM
ERROR [2014-08-27 14:15:16Z]: An exception was thrown while dispatching a method call in the UI thread. System.ArgumentException: CommandLineBuilds restriction cannot be displayed in UI
  at Xamarin.Components.Ide.Activation.ActivationUpgradeWorkflow.ExplainFeatureGroup (System.Collections.Generic.List`1 features, System.String& title, System.String& detail, System.String& listHeader) [0x00109] in /Users/builder/data/lanes/1119/b731d769/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationUpgradeWorkflow.cs:289 
  at Xamarin.Components.Ide.Activation.ActivationUpgradeWorkflow.ExplainFeatures (IList`1 features, System.String& title, System.String& detail, IList`1& detailPopup) [0x000a5] in /Users/builder/data/lanes/1119/b731d769/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationUpgradeWorkflow.cs:206 
  at Xamarin.Components.Ide.Activation.ActivationUpgradeWorkflow.Start (IList`1 features, Xamarin.Components.Ide.Activation.LicenseSyncResult[] results) [0x00020] in /Users/builder/data/lanes/1119/b731d769/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationUpgradeWorkflow.cs:27 
  at Xamarin.Components.Ide.Activation.ActivationService+<FeaturesToWorkflows>c__Iterator0+<FeaturesToWorkflows>c__AnonStorey5.<>m__0 (Xamarin.Components.Ide.Activation.LicenseSyncResult[] r) [0x00007] in /Users/builder/data/lanes/1119/b731d769/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationService.cs:80 
  at Xamarin.Components.Ide.Activation.ActivationService+<GenerateFullWorkflowSequence>c__Iterator4.MoveNext () [0x00053] in /Users/builder/data/lanes/1119/b731d769/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationService.cs:517 
  at Xamarin.Components.Ide.Activation.ActivationDialog..ctor (IEnumerable`1 workflows) [0x0016d] in /Users/builder/data/lanes/1119/b731d769/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationDialog.cs:63 
  at (wrapper remoting-invoke-with-check) Xamarin.Components.Ide.Activation.ActivationDialog:.ctor (System.Collections.Generic.IEnumerable`1<Xamarin.Components.Ide.Activation.ActivationWorkflowStep>)
  at Xamarin.Components.Ide.Activation.ActivationDialog.RunWorkflows (IEnumerable`1 workflows, System.Object parentWindow) [0x00030] in /Users/builder/data/lanes/1119/b731d769/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationDialog.cs:605 
  at Xamarin.Components.Ide.Activation.ActivationService.RunWorkflows (Boolean sync, System.Object parentWindow, System.Func`2[] workflowCreators) [0x0001c] in /Users/builder/data/lanes/1119/b731d769/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationService.cs:510 
  at Xamarin.Components.Ide.Activation.ActivationService.HandleToolErrors (System.Object parentWindow, IList`1 errors) [0x0000e] in /Users/builder/data/lanes/1119/b731d769/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationService.cs:92 
  at Xamarin.Ide.ActivationHelper+<HandleToolErrors>c__AnonStorey1.<>m__0 () [0x00011] in /Users/builder/data/lanes/1119/b731d769/source/md-addins/Xamarin.Ide/Xamarin.Ide/Xamarin.Ide.Accounts/ActivationHelper.cs:76 
  at MonoDevelop.Ide.GenericMessageContainer.Run () [0x00008] in /Users/builder/data/lanes/1119/b731d769/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide/DispatchService.cs:452 
Caller stack not available. Define the environment variable MONODEVELOP_DISPATCH_DEBUG to enable caller stack capture.
Comment 20 troy-dawson 2014-08-27 17:24:37 UTC
Also, I guess I should mention here that the original installer of Xamarin.Mac never finished, I quit first the main installer and then the license key requester, after giving the latter about 5 minutes to do its thing. But XamMac 1.8's working fine for me . . .
Comment 21 troy-dawson 2014-08-27 17:27:10 UTC
Also, yesterday I received a Business trial link; to help isolating this I can cancel my Indie purchase from Monday and see if the problem goes away for me with a Business trial license.
Comment 22 troy-dawson 2014-08-27 17:30:23 UTC
Same error:

/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/MMPTASK: Error MM9008: Building from the command-line requires a Business license. (MM9008) (Scene Kit Session WWDC 2014)

when I try to build the samples/yosemite/SceneKitSessionWWDC2014
Comment 23 Chris Hamons 2014-08-27 17:32:20 UTC
So that error in 19 is associated with an Activation problem. I'd restart XS
and goto Xamarin Studio -> Account and log out / in to your account. If that
doesn't fix it, you'll need to contact support:

http://support.xamarin.com

to get that sorted out.

The one you are seeing in 22 (if XS thinks you have a business license) is an issue I tracked down today.
Comment 24 troy-dawson 2014-08-27 17:37:18 UTC
Logging out & back in results in the empty Unified project and the WWDC 2014 project giving me the 

/Users/troy/Downloads/SceneKitSessionWWDC2014/SceneKitSessionWWDC2014/MMPTASK: Error MM5306: Missing dependencies. Please install Xcode 'Command-Line Tools' component (MM5306) (Scene Kit Session WWDC 2014)

issue again
Comment 25 Chris Hamons 2014-08-27 17:40:35 UTC
That's good at least. That means the activation issue "solved" itself, and now we're back to the ibtool issue most likely.

I'm still trying to track down the issue (won't reproduce for me). Can you post the full build log for that error.
Comment 26 troy-dawson 2014-08-27 17:46:04 UTC
Created attachment 7840 [details]
Unified project template build error

Adding build error as attachment
Comment 27 troy-dawson 2014-08-27 17:55:22 UTC
fwiw wrt:

xcrun -sdk macosx clang -v -mmacosx-version-min=10.6 -arch x86_64 /Library/Frameworks/Xamarin.Mac.framework/Versions/1.11.0.1/lib/libxammac.a -o bin/Debug/test8.app/Contents/MacOS/test8 -D_THREAD_SAFE -I/Library/Frameworks/Xamarin.Mac.framework/Versions/1.11.0.1/lib/pkgconfig/../../include/mono-2.0   /Library/Frameworks/Xamarin.Mac.framework/Versions/1.11.0.1/lib/pkgconfig/../../lib/libmono-2.0.a bin/Debug/test8.app/Contents/MacOS/main.m -framework AppKit -liconv -x objective-c -

main.m is not in bin/Debug/test8.app/Contents/MacOS/

that folder is empty
Comment 28 Chris Hamons 2014-08-27 18:01:17 UTC
Alright, I have a workaround for you.

There appears to be a problem with the apple toolchain in the location /Applications/Xcode6-Beta6.appl/

Try this.

Move /Applications/Xcode.app to some other name
Move /Applications/Xcode6-Beta6.app/ to /Applications/Xcode.app
Restart XS and force a rebuild.

For the people internally have have had this problem, this has solved it for them.

Let me know if that works.
-- Chris H
Comment 29 troy-dawson 2014-08-27 18:13:08 UTC
first trying Xcode6 didn't work, but renaming to Xcode.app worked (and the xcode-select in the CLI step wasn't necessary fwiw)

both the template project and wwdc are building now 

thanks!
Comment 30 Chris Hamons 2014-08-27 18:18:50 UTC
Glad to help. I'm going to update the title and pass it one to figure out why this work around is needed.
Comment 31 troy-dawson 2014-08-27 18:29:34 UTC
yes, it'd be important to note that I only had XCode6-Beta6 on my machine, there was no Xcode.app until I renamed Beta6.
Comment 32 Chris Hamons 2014-08-27 18:31:37 UTC
Yeah, once i explained that to somebody, I think we've found the root cause.
Comment 33 Chris Hamons 2014-08-28 12:31:32 UTC
I tracked it down. Fixed in master / 093666de2c959799b93669eed2c17005459f2992.

It'll be a month or two until this goes public, but at least you have a work around until then.