Interesting idea. Just out of curiosity does it not create another step that you have to keep track of, even in the makefile?
Unless, of course the "touch" target is a dependancy for the release build target..
Quote from: legacy on Yesterday at 10:05:55 pmI prefer having a
bash script that extracts information from { git, mercurial, subversion, doors, ... } such as { commit date, revision, branch, version, author, ... } and fills a C-module created just for the purpose of propagating this information
the bash script is invoked by make, so it has a label ("touch" on my choice) in the Makefile
so make touch ---> creates info.c, it does the job, and you it's a neat job