Walter's suggestion of version.h is pretty standard...

We go the whole-hog method of having our build script call a program to
auto-increment the version (taking into account the branch the script
was requested to build :-), tag the CVS files, check out the source,
build the code, copy the results, etc., etc., etc.

That's probably overkill unless you do a whole lot of builds, but having
your build script collect a version number from the user, tag the files
in your source code control system, and write out a version.h file
wouldn't be too excruciating, I wouldn't think (we used to just pop up
version.h in an editor with "start/wait", but that got to be an
unreliable pain after a while).

Walter Oney wrote:

--
.../ray\..