Re: Current Project Version: Change does not cause rebuild?
Re: Current Project Version: Change does not cause rebuild?
- Subject: Re: Current Project Version: Change does not cause rebuild?
- From: Dirk Stegemann <email@hidden>
- Date: Thu, 6 Apr 2006 23:01:02 +0300
Hello,
Am 06.04.2006 um 21:26 schrieb Scott Tooker:
This is a known bug, which I believe is fixed in the next release
of Xcode. In any case, the behavior you are currently seeing is not
intended.
The work-around for info.plist changes not being recognised is to
close and re-open the project.
At least this works for my (quite simple) projects all the time
(Xcode 2.2.1)
Regards,
Dirk Stegemann
On Apr 5, 2006, at 6:34 PM, Alexander von Below wrote:
In my Project settings, I have set the project version for all my
targets (unless overridden).
CURRENT_PROJECT_VERSION = 1.0.0.39
In the targets, this is included as
<key>CFBundleVersion</key>
<string>${CURRENT_PROJECT_VERSION}</string>
It is imperative that all components have the same version
number, and so the info.plist file for each project should be
updated if the version number is changed. That however does not
seem to be that case. It appears, that the change of the version
is not enough reason to rebuild the info.plist.
Can someone confirm this? Or is this indented behaviour?
Alex
_______________________________________________
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
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
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