Re: [creduce-dev] cmake bug?

I'm currently on vacation but once I'm back next week I can have a look as well if it's still unsolved. Moritz > On 31 Jan 2018, at 05:39, John Regehr wrote: > > I have weak cmake skills but can try to help. > > In any case I just added this as an item on the TODO list so

Re: [creduce-dev] cmake bug?

John Regehr writes: > In souper we have similar foo.in -> foo transformations doing some > substitutions that do get run at "make" time. I don't know if there's > something special about C-Reduce that makes this unworkable. Now that you mention it, I vaguely remember trying

Re: [creduce-dev] cmake bug?

Thanks, I guess I just hadn't run into this before! In souper we have similar foo.in -> foo transformations doing some substitutions that do get run at "make" time. I don't know if there's something special about C-Reduce that makes this unworkable. This is the mechanism we use there:

Re: [creduce-dev] cmake bug?

> John Regehr 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

Re: [creduce-dev] cmake bug?

John Regehr 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

[creduce-dev] cmake bug?

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