Re: [CMake] How to deal with incompatible changes in interface of target_link_libraries()?

2014-08-21 Thread Marcel Loose
On 20/08/14 22:50, Alexander Neundorf wrote: On Tuesday, August 12, 2014 09:06:13 Brad King wrote: ... FYI, the only intended use case for setting a policy to OLD is to quiet warnings in a maintenance branch of an existing release. Some day support for OLD behavior of some policies may be

Re: [CMake] How to deal with incompatible changes in interface of target_link_libraries()?

2014-08-20 Thread Alexander Neundorf
On Tuesday, August 12, 2014 09:06:13 Brad King wrote: ... FYI, the only intended use case for setting a policy to OLD is to quiet warnings in a maintenance branch of an existing release. Some day support for OLD behavior of some policies may be dropped, so all project development moving

Re: [CMake] How to deal with incompatible changes in interface of target_link_libraries()?

2014-08-16 Thread Marcel Loose
Op 12-08-14 om 15:06 schreef Brad King: On 08/12/2014 03:48 AM, Marcel Loose wrote: On a side note. Even using the new PRIVATE and PUBLIC keywords I am unable to exactly specify which libraries are needed for linking. Can you provide a concrete example of this trouble? I've further analyzed

Re: [CMake] How to deal with incompatible changes in interface of target_link_libraries()?

2014-08-12 Thread Marcel Loose
On 11/08/14 18:47, Brad King wrote: On 08/09/2014 09:46 AM, Marcel Loose wrote: CMake 2.8.12 introduced the keywords PRIVATE, INTERFACE and PUBLIC, and immediately deprecated the LINK_INTERFACE_LIBRARIES keyword, triggering policy warnings CMP0022 and CMP0023. What is the proper way to get

Re: [CMake] How to deal with incompatible changes in interface of target_link_libraries()?

2014-08-12 Thread Marcel Loose
On 11/08/14 18:47, Brad King wrote: On 08/09/2014 09:46 AM, Marcel Loose wrote: CMake 2.8.12 introduced the keywords PRIVATE, INTERFACE and PUBLIC, and immediately deprecated the LINK_INTERFACE_LIBRARIES keyword, triggering policy warnings CMP0022 and CMP0023. What is the proper way to get

Re: [CMake] How to deal with incompatible changes in interface of target_link_libraries()?

2014-08-12 Thread Brad King
On 08/12/2014 03:59 AM, Marcel Loose wrote: Another problem I faced with policy CMP0022 is that I was unable to really silence it. Setting the policy to OLD doesn't really work (at least not in my case), maybe because the cmake_policy() command is scoped(?). For CMP0022 and CMP0023 the policy

Re: [CMake] How to deal with incompatible changes in interface of target_link_libraries()?

2014-08-12 Thread Brad King
On 08/12/2014 03:48 AM, Marcel Loose wrote: That's probably in the CMake 3.0.x docs; CMake 2.8.12 doesn't mention LINK_PUBLIC and LINK_PRIVATE in the policy documentation. I only read the following in the docs on target_link_libraries The LINK_PUBLIC and LINK_PRIVATE modes can be used

Re: [CMake] How to deal with incompatible changes in interface of target_link_libraries()?

2014-08-11 Thread Brad King
On 08/09/2014 09:46 AM, Marcel Loose wrote: CMake 2.8.12 introduced the keywords PRIVATE, INTERFACE and PUBLIC, and immediately deprecated the LINK_INTERFACE_LIBRARIES keyword, triggering policy warnings CMP0022 and CMP0023. What is the proper way to get rid of these policy warnings, while

[CMake] How to deal with incompatible changes in interface of target_link_libraries()?

2014-08-09 Thread Marcel Loose
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I'm struggling with the problem that CMake 2.8.12 introduced incompatible changes in the interface of target_link_libraries() w.r.t. dealing with direct and indirect (transitive) link dependencies. Pre-2.8.12 you would use the keyword