Subject: Re: [boost] Build: Trying to get Boost.Build to see my OpenSSL on Windows
From: Vinnie Falco (vinnie.falco_at_[hidden])
Date: 2016-10-01 12:33:30
On Sat, Oct 1, 2016 at 12:24 PM, Steven Watanabe <watanabesj_at_[hidden]> wrote:
> ...
> It assumes that ssl can be found in the default
> library path. You should be able to pass the
> paths to Boost.Build with b2 library-path=... include=...
Wow, that's a huge hassle. And that doesn't scale, what if a project
uses 5 different libraries? You have to pass 10 command line options?
That's incredibly inconvenient... surely this is not the recommended
approach to finding library dependencies...