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.
Thanks,
Tyrel
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
