Re: Projects fail to build
Re: Projects fail to build
- Subject: Re: Projects fail to build
- From: Jens Alfke <email@hidden>
- Date: Tue, 26 Jan 2010 13:35:13 -0800
On Jan 26, 2010, at 1:17 PM, Doug Hill wrote:
If you're making so many changes between one build and the
next that it's difficult to pin down which ones are causing problems,
then slow down. You're programming, not playing Quake. :-)
It doesn't seem like making changes to multiple build settings is
exactly a wild programming practice. If so, Apple should note how
many changes I can make in one session. Also, if they know that
making changes to Xcode projects using their UI leads to corruption,
that would be nice to tell us as well.
Did you read the "if..." part? SOP for isolating problems like this is
to break the changes into smaller groups and test after each one. If
you have to, make one change at a time, test it, and if it works check
it into source control (on a branch if you must.) Then when it breaks,
you'll know the specific change that did it, and can even send Apple
the old and new project files.
Obviously this isn't expected to happen, but stuff happens and you
have to be prepared to work around it.
—Jens _______________________________________________
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