When cmake_refresh_cache() is triggered, always print the cmake regeneration output.
Rationale
This is consistent with the behavior that fprime-util build et al. have when target exists but requires a refresh (e.g. .fpp file was modified). Output of regeneration is printed out.
Imo it helps new users (who may not be familiar with CMake) in understanding the build process. Target doesn't exist -> needs a refresh. Target is out of date -> needs a refresh. Refresh is the same thing happening under the hood in both cases (also fprime-util generate), and the familiar-looking output confirms that.
This has the side effect of also printing the Built target noop to the screen... which I don't really like.
I've been looking in other ways to do this, but was unsuccessful. A fix could be to go in the CMakeHandler._communicate and explicitly skip lines that equal Built target noop\n, but that sounds rather ugly...
Do you have any suggestion?
Change Description
Fix https://github.com/nasa/fprime/issues/1992
When
cmake_refresh_cache()
is triggered, always print the cmake regeneration output.Rationale
fprime-util build
et al. have when target exists but requires a refresh (e.g..fpp
file was modified). Output of regeneration is printed out.fprime-util generate
), and the familiar-looking output confirms that.Comment
This has the side effect of also printing the
Built target noop
to the screen... which I don't really like. I've been looking in other ways to do this, but was unsuccessful. A fix could be to go in the CMakeHandler._communicate and explicitly skip lines that equalBuilt target noop\n
, but that sounds rather ugly... Do you have any suggestion?