AMDG On 10/01/2016 10:33 AM, Vinnie Falco wrote:
On Sat, Oct 1, 2016 at 12:24 PM, Steven Watanabe
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...
No it isn't. This is really a workaround for the user when the author of the Jamfile decided to be lazy. You can also put them in a config file (user-config.jam, site-config.jam, or project-config.jam) like this: project : requirements <library-path>... <include>... ; A better way is to create a module like tools/zlib.jam. In Christ, Steven Watanabe