Le jeu. 30 août 2018 à 20:03, George PF <george....@mail.com> a écrit :
> > The documentation is intriguing about REQUIRED COMPONENTS interaction.... > > That's... one way to put it. > Yeah you know. Kind of ironic here :-) > > So it is possible that the failure behavior when specifying COMPONENTS > is up to the module... > > I admit I was not reading the docs in that depth, but REQUIRED can only > mean one thing and should > not need second guessing the documentation. Sadly, someone thought > otherwise. > I guess there is no one to blame here. The doc is too-realistic about the state of find modules. At least Config mode should do it right I hope. Module mode is historically for hand-written module maintained by volunteers: https://gitlab.kitware.com/cmake/community/wikis/doc/cmake/dev/Module-Maintainers > Do you see this only with Qt or do other packages with components (may be > Boost) behave like this? > > I guess that Qt5 should be running in config mode, whereas boost must be > in module mode though. > > I was debugging an older cmake project and wondered why it was not finding > the non-standard Qt location, > that's when I stumbled upon this issue. > I see. I think something could/should be done for Config mode, for Module mode It would certainly depends on the module maintainer. -- Eric
-- 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: https://cmake.org/mailman/listinfo/cmake
