ExternalProject_Add "configure" step should depend on CMAKE_CACHE_ARGS
We pass values from a parent CMake script through to a child using External_ProjectAdd(CMAKE_CACHE_ARGS <value>)
. When a <value>
that is passed through from the parent changes, the child project's cache is not updated and so continues to use the previous value. I would've expected the child project's cache to be updated to be the same as the new <value>
passed into CMAKE_CACHE_ARGS
.
In the attached (manual) test case, running the first time produces an executable that, when run, produces the text "ChangingThisValueDoesntForceConfigureInChildProject". after changing A_CACHE_VALUE in the top-level project, subsequent builds should display the new value, but still displays "ChangingThisValueDoesntForceConfigureInChildProject".
Edited by Tim Patterson