Comments on: Destroy Xcode Tedium

By: Daniel Jalkut

Daniel Jalkut — Sun, 01 Apr 2007 06:54:03 +0000

I guess if I’m going to use the variable for something different I might as well do Xcode the favor of a new name :)

By: Kevin LaCoste

Kevin LaCoste — Sun, 01 Apr 2007 06:52:48 +0000

I believe that is only true if you’ll be accessing it with agvtool. Xcode doesn’t seem to care what I put in there. Better safe than sorry though eh!

By: Daniel Jalkut

Daniel Jalkut — Sun, 01 Apr 2007 06:27:53 +0000

Thanks, Kevin. I didn’t know about that build setting. But after taking a quick look at it I learn that it’s intended to be a numeric-only value. My value is a string that is intended to be inserted anywhere in a string that the “marketing version” should go. For instance, it helps that I can release builds with APPLICATION_VERSION set to something like “1.0b1″.

By: Kevin LaCoste

Kevin LaCoste — Sun, 01 Apr 2007 06:23:57 +0000

Hey Daniel, nice bit of AppleScript work here.

I just thought I would mention that there is already a build setting in Xcode that does exactly what your “APPLICATION_VERSION” variable is doing. It’s called “CURRENT_PROJECT_VERSION” and it’s not set by default so you can just co-opt it for your script in new projects.

I guess it doesn’t save you much time though. Setting an existing variable versus creating and setting a new one.

By: Red Sweater Blog - Best. Template. Ever.

Red Sweater Blog - Best. Template. Ever. — Tue, 22 Aug 2006 02:42:47 +0000

[...] Centralizes the marketing version in one build setting called “APPLICATION_VERSION.” Just change this build setting to easily update your release version. [...]

By: Jeff LaMarche

Jeff LaMarche — Sat, 24 Dec 2005 22:11:51 +0000

Daniel:

Yeah, it actually does let you bump or set either the build or marketing version, or both. Historically, agvtool has not been the greatest, most stable piece of software to ever come out of Cupertino, but the current version works okay, even with Xcode open (Project Builder didn’t like when you used agvtool while it was up and running). This functionality should be integrated into XCode a little better though, so I’ll give your solution an edge in that regard – I like the command line, but I don’t want to have to use it.

Personally, I still haven’t switched over to Subversion using Xcode yet, though I do use it for my Eclipse projects. Must add it to my list of things I don’t have time to do. :)

By: Daniel Jalkut

Daniel Jalkut — Thu, 22 Dec 2005 15:17:46 +0000

Patrick: I guess I'm not sure exactly what I'd gain by using the preprocessor. I can already do what I need (substitute a build setting for a token) with the solution described here. Adding full preprocessing step seems like an unnecessary complication. Jeff: Does the agvtool allow you to specify a marketing version in build settings? It seems to be much more focused on "build versions," for which I prefer to use a home-grown Subversion-based solution.

By: Jeff LaMarche

Jeff LaMarche — Thu, 22 Dec 2005 14:44:20 +0000

This is pretty cool, but why not just use agvtool with the -all flag? Sure, you have to drop to the command line unless you want to create an AppleScript wrapper, but agvtool, being a supported product specifically designed for assigning, incrementing, and changing XCode project and marketing versions, it seems like in the long run, using agvtool as the basis for automating this process is probably a good idea.

I’m a little hesitant to add a new build setting to accomplish something that there are already build settings for.

Just my 2¢, though, and this probably works fine for you.

By: patrick

patrick — Wed, 21 Dec 2005 20:16:35 +0000

Why don’t you just use plist pre-processing, which was added to Xcode recently? Works for me.