Thanks! This worked for my needs. Ninja said my command line changed. So
I used the generated compile_commands.json before and after a cmake run,
diff'ed those two files and was able to zero in on the issue. Thanks for
the tip. Worked great. Have to store that one away for future use.
--
Mike
Using git like that is actually the perfect way to do it if you just want
to analyze it manually. I've actually done that with other projects source
trees when something seems to appear there even when doing an out of source
build... It's a great way to see what's changed (and how) easily.
You
Does "ninja -d explain" tell you what you need?
On Thu, Nov 24, 2016 at 5:34 AM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> Is there a way to determine which files in my build directory have changed
> for a given run of CMake? The use case is that I made what I thought was a
> small
Is there a way to determine which files in my build directory have
changed for a given run of CMake? The use case is that I made what I
thought was a small change to my configuration using cmake and when I
went to build it was basically a full recompile. During our cmake run we
do use
