On 11/29/2012 04:35 PM, Stephen Kelly wrote:
> I've pushed add-INTERFACE_LINK_LIBRARIES-property to my gitorious clone. Is 
> that what you meant?

I linked the exact commit I meant in 'next'.  I'll look at this one now.

> Is IMPORTED_LINK_DEPENDENT_LIBRARIES different from the others? It doesn't 
> have INTERFACE in the name. I haven't used it before either, but from the 
> documentation, it looks like it should be automatically populated by 
> target_link_libraries(foo LINK_PRIVATE bar) and similar?

It's used to generate -Wl,-rpath-link (or platform equivalent) options
when linking consumers of a library target.  It needs to be populated with
whatever dependencies are linked by the original shared library but are not
in its link interface.  That distinction is per-config and is now harder to
compute.

BTW, have you thought through how CMP0019 will deal with static libraries?
Their IMPORTED_LINK_INTERFACE_LIBRARIES is always the "link implementation"
as specified by tll(), but it is not maintained directly in the original
LINK_INTERFACE_LIBRARIES property.

> I've also pushed a docs commit to my gitorious clone. Please let me know if 
> I can push-merge-rewrite-push-merge that branch. Then I'll rebase the other 
> two topics too.

Feel free to rewrite the staged topics as much as you want to keep things
tested as they evolve from this discussion.

Thanks,
-Brad
--

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

Reply via email to