Re: Projects fail to build
Re: Projects fail to build
- Subject: Re: Projects fail to build
- From: Doug Hill <email@hidden>
- Date: Tue, 26 Jan 2010 13:49:40 -0800
OK, for the record, I'm not making crazy numbers of changes to one project in one sitting. I might change the compiler and then set the appropriate compiler/linker options. Things will seem to work. Then I'll continue working with this project and sometime in the future a project that depends on it will show strange results. Or someone else will build this project on another machine and start getting errors. I haven't spent the time to track down the exact change that results in problems because it's difficult to determine given how these problems show up at seemingly random times. Nothing seems obvious; for example I make a certain change and problems start happening.
I was trying to find out if this is an issue others have seen and perhaps if there are known bugs that I should avoid. As it is, I feel like I'm working blind and that any change could lead to problems.
For example, I created a whole new project. Now a project that depends on it is giving huge numbers of runtime errors of the form:
"unable to read unknown load command 0x80000022"
The only thing I did to the dependent project was to add the new project an tell it to link against its build product.
Seriously, this is getting crazy.
Doug Hill
Oracle Corp.
On Jan 26, 2010, at 1:35 PM, Jens Alfke wrote:
>
> 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