On Mar 23, 2010, at 6:48 PM, Graham Cox wrote: > I'm having a problem making settings in a new target apply in my code. I'm > sure this is really simple and I'm missing something obvious. > > The point is to permit me to release bugfixes to my existing codebase while > moving it forward in a more radical way for future versions. I duplicated my > existing main target and added a user-defined setting to the new target which > value is simply 'YES'. In some parts of my code I conditionalise based on > #ifdef this new setting. > > The problem I'm having is that the condition is never true - it compiles as > if the setting isn't defined. I did a clean build and new target settings > such as the product name are correctly honoured. Why can't my code "see" my > added define? > > --Graham
Graham, I can only suggest with the utmost conviction that you actually fork the code base, [as in, have completely separate 'bug fix' and 'radical change' branches]. Either your radical changes will leak into your bug fix version, or you won't be able to do some change because it will get too complicated to do while maintaining the bug fix version. And if you don't have your code in a version control system that supports branching [and no, CVS does NOT count], you go to your bedroom and think about that while I go and make a switch to punish you with. If you're a one or two-man shop, you can use Perforce for free [with free cli and gui tools to go with the server], and Subversion has gotten better at tracking/merging branches, and the youngun's have a hankerin for git... Eli _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
