Noah Roberts <[email protected]> writes: snip
> I gather I need to create a BlahModule.cmake file that implements the > package finding stuff. I want to install this wherever cmake will find > it. I don't want to put it in some place in the system and then expect > dependent CMakeLists.txt files to set that path when using > find_package. snip > So what is the variable I use in the install() function for the DESTINATION > parameter to do this? I assume there must be one... I can't seem to find > it in the documentation though. Me neither. This answer [1] lists the places that CMake looks for the BlahConfig.cmake file so on Unix it's fairly simple. Set the DESTINATION to 'lib' which will install it to /usr/local/lib/BlahConfig.cmake where, presumable, find_package will locate it. I don't understand how this is meant to work on Windows, though. How is CMake meant to know which root to start thee search under? [1] http://stackoverflow.com/a/11965673/67013 Alex -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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
