configuration dependency on include(...) files?

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

configuration dependency on include(...) files?

Tyrel Newton
Should the cmake configuration step automatically depend on other
included cmake files, i.e. via the include(...) command? We're using
"Unix Makefiles" under version 3.9.

In our project, we have a number of nested include(...) calls to list
source files at various levels (via lots of target_sources calls). When
I touch / change a *.cmake file that is included (even directly) by the
top-most CMakeLists file, it does not trigger the configuration step.

I can certainly list every included *.cmake in the top-most
CMAKE_CONFIGURE_DEPENDS property, but it seems to me that this step
should not be necessary.

Any advice or feedback is appreciated.



Powered by

Please keep messages on-topic and check the CMake FAQ at:

Kitware offers various services to support the CMake community. For more information on each offering, please visit:

CMake Support:
CMake Consulting:
CMake Training Courses:

Visit other Kitware open-source projects at

Follow this link to subscribe/unsubscribe: