On 3/16/10 8:29 AM, Jef Driesen wrote:
On 15/03/2010 22:18, Ralf Wildenhues wrote:
* Jef Driesen wrote on Sat, Mar 13, 2010 at 11:21:45PM CET:
I suppose you are referring to solutions like this:
m4_define([mylib_version_revision],m4_esyscmd([my_revision_script]))
where the revision script fetches the revision from the SCM system,
or from a version file when using tarballs.
Well, that solution has the disadvantage that a revision change causes a
full autotools and configure rerun, but yes, that is one suboptimal
solution.
Is there a better method?
Which method to use depends on where you want the MY_REVISION_VERSION to
propagate. Do you need it in any Makefiles, e.g., or do you only need it
compiled into your program.
Peter
