Re: Plist not being updated
Re: Plist not being updated
- Subject: Re: Plist not being updated
- From: Rainer Brockerhoff <email@hidden>
- Date: Wed, 5 Dec 2007 08:51:47 -0200
At 19:36 -0800 04/12/2007, email@hidden wrote:
>From: Chris Hanson <email@hidden>
>References: <email@hidden>
> <email@hidden>
> <email@hidden>
>In-Reply-To: <email@hidden>
>Date: Tue, 4 Dec 2007 18:42:24 -0800
>Message-ID: <email@hidden>
>
>(1) Follow recommended Mac OS X versioning techniques in one's Info.plist, and use CFBundleShortVersionString for the "marketing version" of your application or framework and CFBundleVersion for its "build version." This shows a version like "2.1 (100)" in the standard About panel above the string supplied by your NSHumanReadableCopyright Info.plist key. Increment the CFBundleVersion value whenever you're going to tag your sources in your SCM repository prior to building a release; setting your Versioning System to "Apple Generic" and using "agvtool new-version -all" will make at least the update-the-version part of this process very straightforward.
I'd tried this option about a month ago. I put "agvtool new-version -all" into the last build phase (bracketed to run only for release builds) and I got constant error messages when building that seemed to imply that agvtool was changing files behind Xcode's back. I suppose that's the wrong way to do it?
>(2) Use build settings judiciously in your Info.plist files. For example, the current Xcode templates specify ${EXECUTABLE_NAME} and ${PRODUCT_NAME} for the values of the CFBundleExecutable and CFBundleName Info.plist keys, respectively. If you have other values that vary based on project or target but otherwise share a common baseline Info.plist file, consider whether you really *need* to use #if/#else/#endif from the C preprocessor to do what you want, or if supplying different build settings from different targets will do what you need.
I have a couple of text files which aren't _the_ Info.plist file where I'd also like some build-time substitution for ${somethings}. Is there any tool I can invoke in a build phase to do that?
TIA,
--
Rainer Brockerhoff <email@hidden>
Belo Horizonte, Brazil
"In the affairs of others even fools are wise
In their own business even sages err."
Weblog: http://www.brockerhoff.net/bb/viewtopic.php
_______________________________________________
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