• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Problems using agvtool during build
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problems using agvtool during build


  • Subject: Re: Problems using agvtool during build
  • From: Claus Broch <email@hidden>
  • Date: Tue, 15 Nov 2005 21:53:46 +0100

Thanks for the reply.

I already have a script that use an external file with automatic CVS commit. I was hoping to be able to change this to the much simpler setup with agvtool, but it looks like I'll just have to stick with what I already have.

Claus

On 15. nov 2005, at 16:50, Chris Espinosa wrote:

On Nov 15, 2005, at 1:14 AM, Claus Broch wrote:

I want to automate my build procedure so the build number of the product is automatically incremented every time I do a release build. I have therefore added the following script phase to the target:

if [ "${CONFIGURATION}" = "Release" ] ; then
	cd "${SRCROOT}"
	/Developer/Tools/agvtool next-version
fi

However every time I build this from inside Xcode it is complaining that it can either not save the project due to some file locking problem or that the project has been changed externally. I know I could just do the build process from xcodebuild but then I would have to close down the project every time I wanted to do a build which is not really a time saver.

agvtool works by modifying the project file, so it's not useful during a build. The way we use it internally is from a shell script that bumps the version number with agvtool, then executes xcodebuild on the project file.


If multiple people build that project file, bumping the version every time somebody builds the Release configuration will create checkin conflicts in your SCM system.

You may want to try a solution that involves a Run Script build phase that writes an .xcconfig file with the CURRENT_PROJECT_VERSION = xx key/value pair, then #include that fine from an .xcconfig file in your target.

Chris



_______________________________________________ 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
References: 
 >Problems using agvtool during build (From: Claus Broch <email@hidden>)
 >Re: Problems using agvtool during build (From: Chris Espinosa <email@hidden>)

  • Prev by Date: Only using host computer to distribute the build
  • Next by Date: Re: Does Xcode 2.2 change a 2.1 project file?
  • Previous by thread: Re: Problems using agvtool during build
  • Next by thread: Allocating a C++ class from obj C
  • Index(es):
    • Date
    • Thread