Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Why does Xcode create nonsensical destinations in every scheme?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why does Xcode create nonsensical destinations in every scheme?

Subject: Re: Why does Xcode create nonsensical destinations in every scheme?
From: G S <email@hidden>
Date: Tue, 24 May 2011 23:05:12 -0700

Never mind. Deleting the lib from the project and re-adding it caused the errors to disappear.

Xcode reliability FTW.

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References:
	>Why does Xcode create nonsensical destinations in every scheme? (From: G S <email@hidden>)
	>Re: Why does Xcode create nonsensical destinations in every scheme? (From: David Duncan <email@hidden>)
	>Re: Why does Xcode create nonsensical destinations in every scheme? (From: G S <email@hidden>)
	>Re: Why does Xcode create nonsensical destinations in every scheme? (From: David Duncan <email@hidden>)
	>Re: Why does Xcode create nonsensical destinations in every scheme? (From: G S <email@hidden>)

Prev by Date: Re: Why does Xcode create nonsensical destinations in every scheme?
Next by Date: RE: Sub-classing NSWindow (i.e. creating a custom title bar)
Previous by thread: Re: Why does Xcode create nonsensical destinations in every scheme?
Next by thread: Why is my Settings.bundle empty?
Index(es):
- Date
- Thread