What I'm hoping for is that find_package() follows the rules it documents here: https://cmake.org/cmake/help/v3.6/command/find_package.html
Specifically, it states it searches these paths (and that <name> is treated case-insensitive): <prefix>/ (W) <prefix>/(cmake|CMake)/ (W) <prefix>/<name>*/ (W) <prefix>/<name>*/(cmake|CMake)/ (W) <prefix>/(lib/<arch>|lib|share)/cmake/<name>*/ (U) <prefix>/(lib/<arch>|lib|share)/<name>*/ (U) <prefix>/(lib/<arch>|lib|share)/<name>*/(cmake|CMake)/ (U) If this is true, then the 3rd one from the top should be a match, because <prefix> is set to: E:/code/frontend/msvc_2015/third_party/installed And <name> is set to ZLIB in find_package() first argument, so it should be adding that to the end. I need to keep CMAKE_PREFIX_PATH pointing to the parent directory ("installed") because I have other libraries that get installed in that directory, each with their own directory to contain their installation files. If find_package() is appending <name> to <prefix> like it says it should, it should find each one of them without switching the value of CMAKE_PREFIX_PATH. Am I misunderstanding something? On Tue, Aug 29, 2017 at 10:06 AM, David Cole <dlrd...@aol.com> wrote: > Shouldn't the "/zlib" at the end be included in your CMAKE_PREFIX_PATH? > > On Tue, Aug 29, 2017 at 11:01 AM, Robert Dailey > <rcdailey.li...@gmail.com> wrote: >> On Tue, Aug 29, 2017 at 9:56 AM, Brad King <brad.k...@kitware.com> wrote: >>> On 08/29/2017 10:55 AM, Brad King wrote: >>>> On 08/29/2017 10:48 AM, Robert Dailey wrote: >>>>> CMAKE_PREFIX_PATH: E:/code/frontend/msvc_2015/third_party/installed >>>>> CMAKE_FIND_ROOT_PATH: E:/code/frontend/msvc_2015/third_party/installed >>>> >>>> I'm not sure how CMAKE_FIND_ROOT_PATH's path re-rooting interacts with >>>> drive letters on Windows. >>> >>> Oops, sent too soon. >>> >>> CMAKE_FIND_ROOT_PATH should not be necessary here. It's for cross-compiling >>> to re-root paths like `/usr` into some prefix on the host. >>> >>> -Brad >> >> Ok but even if I remove that, find_package() still isn't working...... >> -- >> >> 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 -- 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