Hmm, well if that's the case, how does one generate the HelloConfig.cmake file?
Although, for my particular situation, my question about wanting to generate a "Find" file still remains, I think. I have a library which is, potentially, useful to several projects. I assume there's some sort of "Find" template for any such lib, i.e., a project needs to be able to locate a lib (static or dynamic) and headers, cross-platform. thanks, Randy On Mon, Aug 6, 2018 at 4:09 PM, Alexander Neundorf <neund...@kde.org> wrote: > On 2018 M08 2, Thu 10:01:39 CEST Randy Heiland wrote: > > Hi, > > > > I'd like to figure out how to modify the simple "hello" demo ( > > https://cmake.org/examples/) so that the Hello project is a library > with an > > accompanying FindHello.cmake and then the Demo project uses that > > information and "find_package" to discover/use it. > > > > Hopefully that makes sense. Basically, I'm looking for a simple tutorial > on > > how I can make my library easily accessible to a CMake project. > > for that, you don't want a FindHello.cmake (which would typically be > shipped > either by cmake or by the consuming application), instead you want to > generate > and install a HelloConfig.cmake file. > > Alex > >
-- 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
