Stephen Kelly wrote: > INSTALL(EXPORT fooTargets NAMESPACE Foo:: ...) > INSTALL(EXPORT fooTargets EXPORT_INCLUDE_INTERFACE NAMESPACE FooNew:: ...) > > or some other naming change, and include() both in the config file. > > (2) is easy for us and for upstream, but source incompatible for > downstream. (3) is more awkward for all upstreams, but source compatible > for downstream.
Or, of course, (3) could be switched around and NO_EXPORT_INCLUDE_INTERFACE would not populate the INTERFACE_INCLUDE_DIRECTORIES. That would be easier for upstreams, but also leave them potentially accidentally breaking downstreams by not using it when they should. Thanks, Steve. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
