Brad King <brad.king@...> writes: > >> Actually I think this can and should be done for INTERFACE libraries > >> even without IMPORTED_LIBNAME. I'll look at factoring this part out > >> into a preceding commit. > > > > Cool, I think reviewing that separately would be preferable. > > > > I'm interested to see what it looks like without IMPORTED_LIBNAME and where > > the default mapping will come from then, or if there just won't be a default > > mapping until the INTERFACE library becomes 'particular' to something else > > with IMPORTED_LIBNAME. > > I agree. We should resolve configuration mapping for INTERFACE > libraries first. > > I need to revert the 'imported-interface-libname' topic from 'next' > in preparation for the 3.3 freeze anyway. After that we can return > first to INTERFACE configuration mapping and later to link items.
I wonder if you plan do resolve this part in the coming cycle? I think resolving that part would help me to understand the rest of your proposal in the thread. 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-developers
