FROM : Mike Ferris
DATE : Mon Dec 23 19:20:58 2002
Unfortunately, I have it on good authority that the PB rel notes are
mistaken and that feature (referencing build setting values from
Info.plist entries) did not quite make it in for the Dec Tools... Oh
well, something to look forward to for next time I guess.
In the meantime, my favorite way to handle versioning is to use
"apple-generic" versioning and agvtool. This is what many of Apple's
own projects use to do versioning both for source versioning and
"marketing" versions.
In a Terminal do "/Developer/Tools/agvtool help" for full details.
As for how the actual version numbers work, you define a
CURRENT_PROJECT_VERSION build setting with a value that is the string
equivalent of a float (eg 501 or 312.3). You also set CFBundleVersion
to the same number. You set CFBundleShortVersionString to the
"marketing" version (eg 2.0 or 2.1.3). If you have multiple targets
you can set these in all of them as long as you use the same version
numbers for all targets.
When you want to set a new project version use
"/Developer/Tools/agvtool next-version -all". The "-all" makes it
update both the CURRENT_PROJECT_VERSION and CFBundleVersion values.
When you want to set a new "marketing" version use
"/Developer/Tools/agvtool new-marketing-version x.y.z".
(The project should not be open in PB while running agvtool...)
Finder will show the CFBundleShortVersionString in its Version: fields.
Cocoa's standard about panel will show "<CFBundleShortVersionString>
(v<CFBundleVersion)".
At Apple the project version goes up often, at least every time a
version of the project is submitted to the build. The marketing
version goes up at least every time a new version is shipped, but is
more under control of marketing folks who decide whether it should go
up by 1 or 0.1 or 0.0.1 or whatever.
Mike
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
DATE : Mon Dec 23 19:20:58 2002
Unfortunately, I have it on good authority that the PB rel notes are
mistaken and that feature (referencing build setting values from
Info.plist entries) did not quite make it in for the Dec Tools... Oh
well, something to look forward to for next time I guess.
In the meantime, my favorite way to handle versioning is to use
"apple-generic" versioning and agvtool. This is what many of Apple's
own projects use to do versioning both for source versioning and
"marketing" versions.
In a Terminal do "/Developer/Tools/agvtool help" for full details.
As for how the actual version numbers work, you define a
CURRENT_PROJECT_VERSION build setting with a value that is the string
equivalent of a float (eg 501 or 312.3). You also set CFBundleVersion
to the same number. You set CFBundleShortVersionString to the
"marketing" version (eg 2.0 or 2.1.3). If you have multiple targets
you can set these in all of them as long as you use the same version
numbers for all targets.
When you want to set a new project version use
"/Developer/Tools/agvtool next-version -all". The "-all" makes it
update both the CURRENT_PROJECT_VERSION and CFBundleVersion values.
When you want to set a new "marketing" version use
"/Developer/Tools/agvtool new-marketing-version x.y.z".
(The project should not be open in PB while running agvtool...)
Finder will show the CFBundleShortVersionString in its Version: fields.
Cocoa's standard about panel will show "<CFBundleShortVersionString>
(v<CFBundleVersion)".
At Apple the project version goes up often, at least every time a
version of the project is submitted to the build. The marketing
version goes up at least every time a new version is shipped, but is
more under control of marketing folks who decide whether it should go
up by 1 or 0.1 or 0.0.1 or whatever.
Mike
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| Related mails | Author | Date |
|---|---|---|
| matt neuburg | Dec 21, 17:59 | |
| Bill Cheeseman | Dec 21, 23:15 | |
| Sherm Pendley | Dec 22, 00:13 | |
| matt neuburg | Dec 22, 17:22 | |
| Chris Ridd | Dec 22, 20:49 | |
| Greg Hurrell | Dec 23, 00:12 | |
| Sherm Pendley | Dec 23, 04:02 | |
| Greg Hurrell | Dec 23, 06:55 | |
| Mike Ferris | Dec 23, 19:20 |






Cocoa mail archive

