Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Current Project Version: Change does not cause rebuild?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Current Project Version: Change does not cause rebuild?

Subject: Current Project Version: Change does not cause rebuild?
From: Alexander von Below <email@hidden>
Date: Thu, 6 Apr 2006 03:34:58 +0200

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

Follow-Ups:
- Re: Current Project Version: Change does not cause rebuild?
  - From: Scott Tooker <email@hidden>

Prev by Date: Re: A Note on your ADC Confidentiality Agreement
Next by Date: Re: Seeking advice on debugging "real time" programs.
Previous by thread: Re: GetKeys equivalent for Universal Binaries
Next by thread: Re: Current Project Version: Change does not cause rebuild?
Index(es):
- Date
- Thread