Re: managing xcode projects vs going back to makefiles
Re: managing xcode projects vs going back to makefiles
- Subject: Re: managing xcode projects vs going back to makefiles
- From: Dan Korn <email@hidden>
- Date: Wed, 26 May 2010 13:39:20 -0500
On May 26, 2010, at 8:23 AM, Stéphane Beauchemin wrote:
> Another problem with Xcode project is that they can't be edited on a windows computer. The dev that adds an object to a library need to walk to a mac, open the Xcode project make the changes and commit (we haven't found any good remote desktop application for remotely access a Mac from a PC).
I don't understand this development workflow with "blind commits." How can you make changes to projects and commit them, on any platform, without at least making sure they still build? And how can you do that without opening the projects? Even if you're using makefiles or .xcconfig files, how can you be sure that your source code or project changes will work on all of your platforms without trying to build?
I've been doing cross-platform Windows and Mac development for some time, with a mix of projects in multiple versions of Visual Studio, Xcode, CodeWarrior (yep), and makefiles. Whenever I make changes, I need to make sure that they build on all platforms, by going to both Windows and Mac, updating, and then opening projects and building (or running makefiles).
If I'm doing something intensive that risks breaking the build on multiple platforms, then I branch the code using source control, do the work on the branch on one platform, then check that branch out on the other platforms and get it to build before merging back to the mainline.
Dan
_______________________________________________
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