On 03/21/2018 06:01 PM, Craig Scott wrote: > I swear I asked this a while back and there was an example given
Maybe here: * https://gitlab.kitware.com/cmake/cmake/merge_requests/1581 > Does anyone know of a specific example scenario where an > INTERFACE IMPORTED library is the right choice over simply > INTERFACE or IMPORTED on its own? A non-INTERFACE imported target needs an IMPORTED_LOCATION, so an IMPORTED target wouldn't replace an INTERFACE IMPORTED target. A plain INTERFACE library and an IMPORTED INTERFACE library are nearly identical indeed, but the scope of the name differs. IMPORTED INTERFACE libraries mostly exist for install(EXPORT) to produce from an installed/exported INTERFACE library. They can't export as a normal INTERFACE library because imported targets have visibility isolated to the directory that imports them. -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: https://cmake.org/mailman/listinfo/cmake-developers
