First of all, I want to apologize for including the developer list.
Maybe I'm not being patient enough, but it seems like every post I've
made on the normal users list doesn't get any attention.
Secondly, the cmake-packages portion of the cmake documentation
doesn't go into a ton of detail about c
Hi Robert,
On Fri, Sep 1, 2017 at 9:21 PM, Robert Dailey
wrote:
>
> One problem I thought of with the former (one big target.cmake with
> all import targets in there) is that if you only ask for a subset of
> components in find_package(), you will still get all of them since all
> imports are d
On Fri, Sep 1, 2017 at 1:40 PM, Alex Turbov wrote:
> Hi Robert,
>
>
> On Fri, Sep 1, 2017 at 9:21 PM, Robert Dailey
> wrote:
>>
>>
>> One problem I thought of with the former (one big target.cmake with
>> all import targets in there) is that if you only ask for a subset of
>> components in find_p
I've started to use CMake a quite long time ago, and do not search for
"standards" or "guidelines" anymore %)
But I could mention some chapters in the official documentation (in the
"Reference Manuals" section) which are really full of "secret knowledge",
but the problem is that they are too compli
In the case where I'm exporting 1 target.cmake script per component
for a single package, could someone provide an example on how to
manage dependencies? There are 2 types of dependencies:
1. Dependencies on external packages
2. Cross-dependencies within the same package (i.e. on other
components
In my projects I always, have external dependencies with finder module
providing exported (imported in my project) targets, so my targets (one per
file) always have a list of `Vendor::target`. Some of them are mine (i.e.
your type 2 -- built by the same project).
I wrote a helper module and a func
