Re: [CMake] [cmake-developers] How should config packages handle components?

2017-09-06 Thread Alex Turbov
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

Re: [CMake] [cmake-developers] How should config packages handle components?

2017-09-01 Thread Florent Castelli
On 01/09/2017 20:40, 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

Re: [CMake] [cmake-developers] How should config packages handle components?

2017-09-01 Thread Alex Turbov
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

Re: [CMake] [cmake-developers] How should config packages handle components?

2017-09-01 Thread Robert Dailey
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

Re: [CMake] [cmake-developers] How should config packages handle components?

2017-09-01 Thread Alex Turbov
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