Re: Automate build numbers
Re: Automate build numbers
- Subject: Re: Automate build numbers
- From: Chris Espinosa <email@hidden>
- Date: Fri, 25 Aug 2006 23:01:13 -0700
On Aug 25, 2006, at 5:41 PM, Jerry Krinock wrote: YES! That worked! Very strange. So, as you can see from the final, working Info.plist file which I've pasted in below, the things that Xcode replaces DO want the ${...}, but the things that the gcc preprocessor replaces do NOT want the ${...}. Intuitive!!
Now I understand why Apple hasn't gotten around to writing any detailed documentation on this. I think I'll go clean my garage....
- a way to substitute Xcode build settings in plists - a way for plists to expand C macros from #include files
Both are valid and useful, but they have to be a) consistent with their natures and b) separable from each other so they don't step on each other.
Xcode build settings are always expanded with the ${SETTING_NAME} notation, and C macros are always expanded wherever found in the text.
Chris |
_______________________________________________
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