Re: [CMake] What are the actual benefits of namespaced targets?

2018-03-11 Thread Alan W. Irwin
On 2018-03-11 10:15+0100 Nils Gladitz wrote: On 10.03.2018 23:01, Alan W. Irwin wrote: Anyhow, your thoughts would be appreciated for reasonable best practice limits on how far (if any) beyond the common code case you would go to convert an old project to use ALIAS libraries and modules in the

Re: [CMake] What are the actual benefits of namespaced targets?

2018-03-11 Thread Nils Gladitz
On 10.03.2018 23:01, Alan W. Irwin wrote: Anyhow, your thoughts would be appreciated for reasonable best practice limits on how far (if any) beyond the common code case you would go to convert an old project to use ALIAS libraries and modules in the build tree that have to be implemented in any c

Re: [CMake] What are the actual benefits of namespaced targets?

2018-03-10 Thread Alan W. Irwin
On 2018-03-08 12:49-0800 Alan W. Irwin wrote: On 2018-03-08 20:05+0100 Nils Gladitz wrote: On 08.03.2018 19:50, Alan W. Irwin wrote: So what are the actual benefits of namespacing the exported targets associated with libraries? On the consumer side it makes linking to targets less error pr

Re: [CMake] What are the actual benefits of namespaced targets?

2018-03-08 Thread Alan W. Irwin
On 2018-03-08 20:05+0100 Nils Gladitz wrote: On 08.03.2018 19:50, Alan W. Irwin wrote: So what are the actual benefits of namespacing the exported targets associated with libraries? On the consumer side it makes linking to targets less error prone. When you link to a library target without

Re: [CMake] What are the actual benefits of namespaced targets?

2018-03-08 Thread Nils Gladitz
On 08.03.2018 19:50, Alan W. Irwin wrote: So what are the actual benefits of namespacing the exported targets associated with libraries? On the consumer side it makes linking to targets less error prone. When you link to a library target without a namespace and e.g. get the name or scope wro

[CMake] What are the actual benefits of namespaced targets?

2018-03-08 Thread Alan W. Irwin
I am currently trying to update three CMake-based build systems (for PLplot, ephcom, and te_gen) to use best practices following the really useful example of best practice given at . That example uses the NAMESPACE signature f