Re: [CMake] configuration packages, IMPORTED targets, and global scope

Thanks, I am watching that discussion and will try to contribute where I can. On Thu, Sep 7, 2017 at 4:02 AM, Deniz Bahadir wrote: > Am 06.09.2017 um 20:24 schrieb Robert Dailey: >> >> So it took me a while to figure out why find_package() calls I was >> making (with CONFIG)

Re: [CMake] configuration packages, IMPORTED targets, and global scope

Am 06.09.2017 um 20:24 schrieb Robert Dailey: So it took me a while to figure out why find_package() calls I was making (with CONFIG) option were not accessible outside of the directory in which it was invoked. I realized that all targets seem to be global by default except IMPORTED targets

[CMake] configuration packages, IMPORTED targets, and global scope

So it took me a while to figure out why find_package() calls I was making (with CONFIG) option were not accessible outside of the directory in which it was invoked. I realized that all targets seem to be global by default except IMPORTED targets (according to add_library() docs). I find this