Why not just use configure_file to write ${metals} into the file...
configure_file only actually touches/writes-to/updates the file if the
contents are different...
Then you can just depend on that file and you don't need a separate
timestamp file.
HTH,
David C.
On Tue, Jun 9, 2015 at 1:05
On 2015-06-09, at 8:05 AM, David Cole dlrd...@aol.com wrote:
Why not just use configure_file
because I didn’t know about it. Thanks!
to write ${metals} into the file...
configure_file only actually touches/writes-to/updates the file if the
contents are different...
Then you can just
First, my cmake code does this:
sets ${metals} from a cmake command-line argument
compares the contents of ${metals} against the contents of a file to note
whether the variable is being changed since the last run of cmake
writes the new value to that file for next time
call an