On 11/09/2016 01:28 PM, maikel van den Hurk wrote:
>> Stephen Kelly wrote:
>> I believe it's because of a chicken-egg concern - the link libraries are the
>> basis for transitivity for other properties. I remember discussing that in
>> the mailing list back in the design phase.
>
> When trying to
16 01:23
Aan: cmake-developers@cmake.org
Onderwerp: Re: [cmake-developers] Add property to get all linked libraries
including transitive ones
Brad King wrote:
> On 11/04/2016 09:52 AM, maikel van den Hurk wrote:
>> What about doing what was targeted with this bug:
>> https://cmake
Brad King wrote:
> On 11/04/2016 09:52 AM, maikel van den Hurk wrote:
>> What about doing what was targeted with this bug:
>> https://cmake.org/Bug/view.php?id=12435?
>
> That issue is now tracked here:
>
> https://gitlab.kitware.com/cmake/cmake/issues/12435
>
> I've just added some notes to t
Thanks for tracking the issue! Just checked the code and there is the following
part
https://gitlab.kitware.com/cmake/cmake/blob/v3.6.3/Source/cmGeneratorExpressionNode.cxx#L944
which you will hit when adding LINK_LIBRARIES to the list of items to expand
transitively. If I understand this part
On 11/04/2016 09:52 AM, maikel van den Hurk wrote:
> What about doing what was targeted with this bug:
> https://cmake.org/Bug/view.php?id=12435?
That issue is now tracked here:
https://gitlab.kitware.com/cmake/cmake/issues/12435
I've just added some notes to the discussion.
Steve, do you rec
.
Van: Brad King
Verzonden: donderdag 3 november 2016 12:53
Aan: maikel van den Hurk
CC: cmake-developers@cmake.org; Tobias Hunger
Onderwerp: Re: [cmake-developers] Add property to get all linked libraries
including transitive ones
On 11/02/2016 04:23 PM, maikel van den Hurk wrote:
>
On 11/02/2016 04:23 PM, maikel van den Hurk wrote:
> We are trying to develop a proper C++ dependency management tool
> ...be able to get all transitive linked libraries
The cmake-server mode introduced in 3.7 was created to support tooling.
Perhaps something with that can be made to work if it do
One usage I would have had for this feature would have been to generate
a pre-linked library.
Basically, merging a static library and its dependencies together (check
ld -r) and output an object file for static linking (not a shared library).
This is required as merging static libraries may confl
We are trying to develop a proper C++ dependency management tool which will
combine Ivy together with CMake. Our intention is to open source this this
modules later for everyone.
As we need to keep track of all dependencies we would like to be able to get
all transitive linked libraries to be a
On 11/01/2016 04:30 PM, maikel van den Hurk wrote:
> obtain actually all transitive linked libraries of a specific target.
[snip]
> this information is only fully available during generation time.
What is an example use case for this? I don't think we can offer a
configure-time solution but perha
It would be nice to extend the current properties set of LINK_LIBRARIES and
INTERFACE_LINK_LIBRARIES with a property to obtain actually all transitive
linked libraries of a specific target. Currently you will have to traverse
yourself over all targets to get in CMake a full overview of all linke
11 matches
Mail list logo
