On 08/12/2014 03:48 AM, Marcel Loose wrote: > That's probably in the CMake 3.0.x docs; CMake 2.8.12 doesn't mention > LINK_PUBLIC and LINK_PRIVATE in the policy documentation. I only read > the following in the docs on target_link_libraries > > The LINK_PUBLIC and LINK_PRIVATE modes can be used to specify > both the > link dependencies and the link interface in one command. This > signature is for compatibility only. Prefer the PUBLIC or PRIVATE > keywords instead. > > "... for compatibility only" didn't give me the feeling that this is the > way to go, which is underscored by the next sentence: "Prefer the ..."
If your project requires CMake 2.8.12 or higher then it is preferred to use PUBLIC/PRIVATE. For compatibility with earlier CMake versions you can still use LINK_PUBLIC/LINK_PRIVATE. > On a side note. Even using the new PRIVATE and PUBLIC keywords I am > unable to exactly specify which libraries are needed for linking. Can you provide a concrete example of this trouble? -Brad -- 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
