Alexander Neundorf wrote:
On Tuesday 05 May 2009, alexandre.feb...@thomsonreuters.com wrote:
I saw this too.
IMHO, it's a bug. If it's a feature, I don't see the point.
I think it's a feature that imported targets are not global. Brad explained
this in a mail not too long ago, but I don't rem
On Tuesday 05 May 2009, alexandre.feb...@thomsonreuters.com wrote:
> I saw this too.
> IMHO, it's a bug. If it's a feature, I don't see the point.
I think it's a feature that imported targets are not global. Brad explained
this in a mail not too long ago, but I don't remember the details.
Alex
_
Maybe someon from Kitware could comment on this?
On Tue, May 5, 2009 at 6:38 PM, wrote:
> I saw this too.
> IMHO, it's a bug. If it's a feature, I don't see the point.
>
> I ended defining all my imported targets in the top directory, to be
> able to use them wherever I need them.
Unfortunately
.org] On Behalf
Of Pentasopor
Sent: Tuesday, 05 May 2009 18:06
To: cmake@cmake.org
Subject: [CMake] using IMPORTED targets in multiple projects within one
CMake tree
Hi all,
here is what I'm trying to do:
I have a CMake build tree with several projects and targets with some
depending on o
Hi all,
here is what I'm trying to do:
I have a CMake build tree with several projects and targets with some
depending on others (impressive eh? ;)). Furthermore I have a library
that I need to build outside of CMake and therefor I just added it
using
> add_library(xxx SHARED IMPORTED)
(But an
