Building binary with a version number and meta data

[puzzlecracker]

Guys,

i'm building a c++ app, and want to include a standard version and
other relavant info, like a build data. Hence a user can do ./app -r
and will have the info available.

What is the standard pattern for that? I imagine that some of that
should be read from the file.


Thanks

 

[red floyd]

Guys,

i'm building a c++ app, and want to include a standard version and
other relavant info, like a build data. Hence a user can do ./app -r
and will have the info available.

What is the standard pattern for that? I imagine that some of that
should be read from the file.

I'd just use a version.h file.

 

[puzzlecracker]

I'd just use a version.h file.

Would you point to an example, perhaps of an open source?


Thanks

 

[Ian Collins]

Would you point to an example, perhaps of an open source?

A common technique is to have an header with either a manual or embedded
SCM version number.

 

[Rüdiger Ranft]

Guys,

i'm building a c++ app, and want to include a standard version and
other relavant info, like a build data. Hence a user can do ./app -r
and will have the info available.

You may consider -V or --version, like many other programms do.

What is the standard pattern for that? I imagine that some of that
should be read from the file.

Usual you build a header containing a constant with your programm
version like this:

#ifndef MY_PROG_VERSION_H__
#define MY_PROG_VERSION_H__

#define MY_PROG_VERSION_STRING "1.2.3.4-a-foo.bar"

#endif

and include this everywhere you need the version. When you use a
version control system you can also generate this header to fill the VCS
revison info into the version number.

bye
Rudi

 

[red floyd]

You may consider -V or --version, like many other programms do.


Usual you build a header containing a constant with your programm
version like this:

#ifndef MY_PROG_VERSION_H__
#define MY_PROG_VERSION_H__

#define MY_PROG_VERSION_STRING "1.2.3.4-a-foo.bar"

#endif

and include this everywhere you need the version. When you use a
version control system you can also generate this header to fill the VCS
revison info into the version number.

OT, but kill the second trailing underscore. Double underscores are
reserved to the implementation.