Thanks for the reply, Michi. Forgive me if I'm missing something - how does
this help with your package config file? Doesn't Boost_LIBRARIES contain full
paths to the component libraries you listed? My understanding is that in
order to have a package config file result in something that can
> -Original Message-
> From: Ruslan Baratov [mailto:ruslan_bara...@yahoo.com]
> Sent: Wednesday, January 27, 2016 2:18 AM
> To: Johnson, Matt (GE Healthcare)
> Cc: cmake@cmake.org
> Subject: Re: [CMake] What is the best way to handle Boost dependencies in
> a package config file
>
> On
On 27-Jan-16 20:08, Johnson, Matt (GE Healthcare) wrote:
-Original Message-
From: Ruslan Baratov [mailto:ruslan_bara...@yahoo.com]
Sent: Wednesday, January 27, 2016 2:18 AM
To: Johnson, Matt (GE Healthcare)
Cc: cmake@cmake.org
Subject: Re: [CMake] What is the best way to handle Boost
We use this, which works fine for me on Ubuntu:
find_package(Boost COMPONENTS system filesystem regex serialization thread log
REQUIRED)
Cheers,
Michi.
> On 27 Jan 2016, at 12:54 , Johnson, Matt (GE Healthcare)
> wrote:
>
> I like package config files. I want
On 27-Jan-16 09:54, Johnson, Matt (GE Healthcare) wrote:
I like package config files. I want to use more of them. However, I have a
dependency on boost. While boost has a Find module, it doesn't have a package
config file. I'm not going to be able to depend on the users of my package
I like package config files. I want to use more of them. However, I have a
dependency on boost. While boost has a Find module, it doesn't have a package
config file. I'm not going to be able to depend on the users of my package
building boost via cmake (also, is that still an active