Domen Vrankar wrote: > I've started solving this a while ago with treating every library as > an external dependency even if it is part of the same repository as > the code for the executable. > For every new library that I write I also write a FindSomeLib.cmake
Much of what you describe should not be necessary in a modern CMake system. http://www.cmake.org/cmake/help/v3.0/manual/cmake-packages.7.html http://www.cmake.org/cmake/help/v3.0/manual/cmake-buildsystem.7.html#alias-targets http://www.cmake.org/cmake/help/v3.0/command/export.html#command:export Thanks, Steve. -- 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
