John Regehr <reg...@cs.utah.edu> writes: > There's something weird going on where the "creduce" file isn't getting > generated from "creduce.in" after I modify the latter. So I change > creduce.in, run "make install", and then I just get the old version of the > file. I can get the newer version if I remove my build directory and run > cmake again. Might this be related to recent changes?
tl;dr run cmake again? `creduce` is generated from `creduce.in` when you run cmake, not when you run make. I.e., it is generated at "configure time," not "build time." This is different than the Autoconf-based path, where `creduce` is generated when make is run. AFAIK, there is not a cmake command that is the equivalent of "run sed on this file when make is run." Cmake can do substitutions, but of couse this happens when cmake itself is run. I agree with you that it would be preferable for `creduce` to be generated when make is run, as in the Autoconf-based path. I don't know how to do this portably. I would be happy to be educated! I forget if simply running cmake again is good enough to do what you want. Eric. -- ------------------------------------------------------------------------------- Eric Eide <ee...@cs.utah.edu> . University of Utah School of Computing http://www.cs.utah.edu/~eeide/ . +1 (801) 585-5512 voice, +1 (801) 581-5843 FAX