There is an optimization in pkg_check_modules that skips processing
once a successful execution has occurred and simply leaves the cached
return variables as is. As currently implemented, any changes to the
parameters of pkg_check_modules, excluding PREFIX, will be ignored
following a successful execution. Workarounds include modifying the
PREFIX and all references to it, or starting over from an empty build
directory. Adding a pkg-config dependency after the initial
configuration is a regular part of our development workflow and the
existing workarounds are cumbersome.
I would like to enhance the behavior of pkg_check_modules to store the
parameters for a given PREFIX so that changes to those parameters can
disable the optimization and re-evaluate pkg_check_modules.
Are there any concerns about or objections to adding this behavior?
If not, should this change in behavior be noted in the documentation?
--
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-developers
