Nils I wasn’t setting xxx_FOUND at all - and I never resolved this problem, but it went away on its own after I made some changes to various config files etc.
Thanks anyway. JB On 16/09/14 18:08, "Nils Gladitz" <nilsglad...@gmail.com> wrote: >On 16.09.2014 17:38, Biddiscombe, John A. wrote: >> " >> Found package configuration file: >> >> /Users/biddisco/build/cmakesuper/xxx/xxx-config.cmake >> >> but it set xxx_FOUND to FALSE so package “xxx" is >> considered to be NOT FOUND. >> “ >> >> Which is not expected. If I set xxx_FOUND in the config, it goes away, >>but I was under the impression that the cmake find_package command >>itself should set the xxx_FOUND internally and not be done by the user. >> >> Is the find_package command trying to tell me something by showing this >>message? > >It think the message indicates that the config file was setting >xxx_FOUND explicitly to FALSE itself. > >Nils -- 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
