Stephen Kelly wrote: > Currently, in the add-INTERFACE_LINK_LIBRARIES-property branch, the > INTERFACE_LINK_LIBRARIES property is read for static libraries if the > policy is new,
I've changed that now in the branch. Effort is made to not populate the property, and even if it does get populated, the value is not exported. > even though it is LINK_LIBRARIES that we want to read in > the case of STATIC libraries. That can only really be addressed when my > followup topic to introduce the LINK_LIBRARIES property is merged. The > question is how to deal with that? > > I can update add-INTERFACE_LINK_LIBRARIES-property to skip reading > INTERFACE_LINK_LIBRARIES for STATIC libraries, and then revert that later > when LINK_LIBRARIES is in, or I could simply not add such a patch, in the > understanding that the case for STATIC libraries will be handled in a > future topic. The patch I added does not need to be reverted. So we're just left in an intermediate state temporarily where exported static libraries do not get their INTERFACE_LINK_LIBRARIES populated, even when they should. That can be fixed when the followup topic is merged. 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
