Hi, Current CMake disallows Interface Libraries to have dependencies. However, I suspect that was done for a reason. Here is the commit for that change:
commit 6db7e6d24c68085f16dcf6d8a86ae0f74e9a1f01 Author: Stephen Kelly <[email protected]> Date: Wed Dec 25 15:11:50 2013 +0100 add_dependencies: Disallow use with INTERFACE_LIBRARY. It says what it does but not why... >From CMake documentation: "A primary use-case for INTERFACE libraries is header-only libraries". But what if those headers are generated during build time? Or what if it depends on libraries that are part of the build? Or what if that library is a result of ExternalProject_Add()? I though about it and I can't come with any idea why that was explicitly disallowed. Maybe it's possible to allow it back? Any ideas? -- 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
