On Mon, Jul 27, 2015 at 14:56:26 -0400, Brad King wrote: > The error on not exporting private dependencies has received > complaints before. Technically it is necessary to properly > populate the -rpath-link flag when a shared library has > dependencies that are not next to it and not in a standard > location, but often it is not necessary in practice. I think > we once discussed dropping the error and populating the > IMPORTED_LINK_DEPENDENT_LIBRARIES property only with private > dependencies that happen to be available in the export set. > The discussion may be in the dev list archives but I don't > recall when/where.
Wouldn't an exported static library still need to inform others about its private non-exported static library dependencies though? For a shared library, ignoring static libraries in the private set would make sense. --Ben -- 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-developers
