Re: Advice request on Xcode configuration for long term project.
Re: Advice request on Xcode configuration for long term project.
- Subject: Re: Advice request on Xcode configuration for long term project.
- From: Garvan Keeley <email@hidden>
- Date: Thu, 3 Dec 2009 16:52:47 -0500
We have a large build system that builds multiple dynamic libs (25 or so), in various configurations, coming from different companies, on multiple platforms.
I highly recommend you investigate the xcconfig system of XCode if you want something highly scaleable (it is source control merge-able, uses Makefile-like syntax, can be updated by developers on any platform). It uses key-value pairs in a text file for your project settings. You could translate your existing build settings to an xcconfig file, and then create an xcode project that uses this for its build settings. If you really want to get fancy, you could probably find a way to commonize the key-value pairings used for your linux build settings into some base file that gets picked up by both the linux and xcode build systems.
That being said, we ended up wanting more than xcconfig would provide, and now use qmake to generate our xcode projects (cmake also looked promising for this purpose).
I guess my reply doesn't address which is better, the 1 giant project option or the 45 tiny projects option. Certainly the former sounds more convenient for a small number of developers, the latter more modular for multiple developers to work on. Having worked on both types of projects, I find the 1 giant project with multiple targets does seem a easier to work with in terms of navigation/searching/managing breakpoints.
Cheers,
Garvan.
_______________________________________________
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