On 06/07/2013 09:20 AM, Stephen Kelly wrote: > Brad King wrote: >> Don't you mean LINK_INTERFACE_LIBRARIES there? > > Yep, I fixed it and pushed it to my clone.
Great. One more part to think about is how the warning can work for the interface policy. In what I proposed: * OLD behavior uses the old properties for everything (tll sets them, cmTarget reads them) * NEW behavior uses the new property for everything (tll sets it, cmTarget reads it) Note that in the NEW behavior, even the old-style tll LINK_INTERFACE_LIBRARIES signature will set the new property. When the policy is not set we will use the old behavior, but when would we ever warn to ask developers to set the policy? It can't be triggered by "new-style" code because the whole point of policy warnings is to trigger for old code not yet aware of the policy and the preferred new behavior. Perhaps we can warn whenever someone sets the old property explicitly through set_property or set_target_properties such that it would not be mapped by the policy's changes to tll behavior. Other ideas? We could also warn when someone sets the new-style properties but does not set the policy to NEW. -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