Re: Automate build numbers
Re: Automate build numbers
- Subject: Re: Automate build numbers
- From: Greg Guerin <email@hidden>
- Date: Fri, 25 Aug 2006 12:02:27 -0700
Jerry Krinock wrote:
> <key>CFBundleVersion</key>
> <string>${RELEASE_VERSION}</string>
> ..snip..
>******* "Output" Info.plist in product Contents/, produced by Xcode:
> ..snip..
> <key>CFBundleVersion</key>
> <string></string>
I suspect that the source text "${RELEASE_VERSION}" is being replaced
before gcc's preprocessor ever gets run. This would be happening because
${RELEASE_VERSION} looks like a replaceable Xcode variable, so if the value
of RELEASE_VERSION is nil or empty, it gets replaced by nothing. You're
the victim of colliding replacement mechanisms.
A way to test this hypothesis would be to define a build setting for
RELEASE_VERSION that differs from the value you assign it in your
preprocessor definition, and then see what the output Info.plist is.
Gcc's C preprocessor doesn't need ${} surrounding its replaceable elements.
It's just a normal C preprocessor working on plain text in ordinary macro
mode. I think if you remove the ${} from RELEASE_VERSION it will work.
Also see this past post:
<http://lists.apple.com/archives/cocoa-dev/2005/Dec/msg01384.html>
and in this one, note:
<http://lists.apple.com/archives/xcode-users/2005/Nov/msg00227.html>
"* Preprocessing Info.plist adds whitespace that causes XML parse failure
Using the Preprocess Info.plist feature may produce an invalid XML file.
Adding the -traditional flag to 'Info.plist Other Preprocessor Flags' may
help."
-- GG
_______________________________________________
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