[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Is there an ultimate solution for the build process/global revision number

From: Bill Arnette <billa_at_signalscape.com>
Date: 2005-06-29 15:37:49 CEST

We keep a build.number file in the root of the project. Whenever we build,
we increment the build number, commit the build.number file, and then do the
build. After the build is complete, we tag the project with the build
number. We use NAnt to drive the build and set a property equal to the
build number to use for tagging the build.

I'm not a VB programmer so I am not sure about how to get the build number
into your about box at compile time (maybe use a script to modify a
well-known global variable?). But there is a tool I use called StampVer [1]
that updates the VERSION resource in a Win32 executable. We run this on all
exes/dlls after the build is complete and the about box/splash screen uses
the Version APIs to retrieve it, and display it. This has the advantage of
marking all the files with the same version if you use explorer to examine a
file's properties.

[1] http://www.elphin.com/products/stampver.html

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 29 15:40:54 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.