Jc, That is precisely what I do for superbuild. This applies to non superbuilds, its also helpful if we are running on a cluster, supercomputers or machines that it is difficult to access the web (though superbuild URLs can be local paths too). Its also helpful for people running multiple versions (i.e. developers). Lastly, it meshes well with our legacy makefile system. Some packages cannot be integrated with superbuild as easily because of license restrictions, so we need a way to search for these packages.
Im wondering why there isn't a way to pass paths to find_package in module mode already. If this would be a good feature, I would consider contributing a patch myself to add this in. Either making find_package(FOO HINTS path/to/something) not force config mode and pass the hint to FindFoo, or adding a new argument as find_package(Foo MODULE_HINTS /path/to/something), or similar. Thoughts? -Jameson -- View this message in context: http://cmake.3232098.n2.nabble.com/Confusion-regarding-usage-of-find-package-and-PATHS-or-HINTS-tp7587611p7587721.html Sent from the CMake mailing list archive at Nabble.com. -- 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
