> If your trees are so huge or import so many other third-party projects that
> name collisions are a problem
They are. I'm predicting possible collisions, but it's ok for now.
> ... ExternalProject.
Not much suitable.
---
Ok, I'll try to do some workarounds. Thanks for the replies.
On 12 De
On 12/12/2016 11:35 AM, Egor Pugin wrote:
> So, the original proposal is to make ALIAS & OBJECT targets local. And
> explicit GLOBAL keyword will make them global again.
An OBJECT library is just like any other target as far as the generated
build system is concerned, so it needs a globally unique
So, the original proposal is to make ALIAS & OBJECT targets local. And
explicit GLOBAL keyword will make them global again.
On 12 December 2016 at 18:37, Brad King wrote:
> On 12/10/2016 04:13 PM, Egor Pugin wrote:
>> Is it possible to add GLOBAL option as for INTERFACE/IMPORTED targets
>> (lib/
On 12/10/2016 04:13 PM, Egor Pugin wrote:
> Is it possible to add GLOBAL option as for INTERFACE/IMPORTED targets
> (lib/exe)?
The GLOBAL option is only available with an IMPORTED target:
https://cmake.org/cmake/help/v3.7/command/add_library.html#imported-libraries
Non-imported targets are alw
Hi,
It seems we don't have such feature at the moment.
https://cmake.org/cmake/help/v3.7/command/add_library.html?highlight=add_library#alias-libraries
Is it possible to add GLOBAL option as for INTERFACE/IMPORTED targets (lib/exe)?
For consistency it's also possible to add GLOBAL for OBJECT libs
