Re: [cmake-developers] [CMake] Why does INTERFACE type targets only support whitelisted properties?

On Mon, Jan 11, 2016 at 5:16 PM, Stephen Kelly wrote: > Taylor Braun-Jones wrote: > >> Consider library project Foo that uses a header-only project Bar. In >> FooConfig.cmake, it is a important to ensure any projects using Foo also >> use the exact same version of Bar that Foo

Re: [cmake-developers] [CMake] Why does INTERFACE type targets only support whitelisted properties?

On Mon, Jan 11, 2016 at 16:47:03 -0500, Taylor Braun-Jones wrote: > I have another INTERFACE property use case that is not whitelisted, but > should be: VERSION VERSION is a special property for libraries. Particularly the name for the file with the actual content of the library (the SOVERSION

Re: [cmake-developers] [CMake] Why does INTERFACE type targets only support whitelisted properties?

On Fri, Jan 8, 2016 at 9:12 AM, Nils Gladitz wrote: > > > On 01/08/2016 02:50 PM, Yves Frederix wrote: > >> You are explicitly mentioning 'setting' of a property. IMHO there is a >> big difference between setting and getting a property. If >> white/blacklisting is enforced