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
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
On 11/02/2016 03:32 PM, Levi Morrison wrote:
> Brad, here it is a year later and thought I would get around to
> finishing this work. Then I discovered you had already completed it!
> Thank you so much!
>
> I now have access to the 2017 Intel C++ compiler; is there anything in
> particular you'd
On Wed, Dec 2, 2015 at 8:40 AM, Brad King wrote:
> On 12/02/2015 10:31 AM, Levi Morrison wrote:
>> Hmm. What is the purpose of this module? I verified that indeed my
>> changeset somehow breaks this test but I don't even understand what it
>> is trying to do. At a glance it
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