One alternative is to use git itself. There is a "git smudge" option that can do much of what you are asking. However, I've never done this sort of thing.
http://progit.org/book/ch7-2.html Just $0.02, -dan On 7/8/10 3:31 PM, "Tyler Roscoe" <ty...@cryptio.net> wrote: > On Wed, Jul 07, 2010 at 10:43:15PM -0400, John Drescher wrote: >> On Wed, Jul 7, 2010 at 9:44 PM, Clark Gaebel <cg.wowus...@gmail.com> wrote: >>> I would like to generate file that looks something like this: >>> >>> // version.h >>> #define VERSION "v0.1-345-ga77ede8" >> >> You want to do that with configure_file > > The upside of this approach is that it's simple. The downside is that it > is only run (and thus your version header is only updated) whenever > CMake runs. It's possible for the source code to change without > triggering a re-run of CMake. > > Consequently, we use a custom command to call a python script at build > time. The script writes out the header with the up-to-date version info. > > tyler > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake -- Daniel Blezek, PhD Medical Imaging Informatics Innovation Center P 127 or (77) 8 8886 T 507 538 8886 E blezek.dan...@mayo.edu Mayo Clinic 200 First St. S.W. Harwick SL-44 Rochester, MN 55905 mayoclinic.org _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake