If my package is installed to a non-standard location, my <PROJECT>Config.cmake file is currently also installed to the non-standard location and can't be found by dependent projects.
I see that there's export(PACKAGE <PROJECT>), but this creates an entry in the registry for the build location of the PROJECT rather than the installed location. Is there some way I can install target files to a non-standard location but be sure that <PROJECT>Config.cmake can be found without explicitly installing it into something like /usr/lib/cmake/PROJECT? Thanks, -- Andrew Bell [email protected]
-- 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
