Vinnie Falco wrote:
On Sat, Oct 1, 2016 at 6:05 PM, Peter Dimov
wrote: Based on how it's written, the expectation is probably that the INCLUDE and LIBPATH environment variables contain the appropriate OpenSSL directories. That's the closest thing on Windows to "system" include/library paths.
That sounded promising so I set these variables in the environment but I'm still not having any luck building the SSL Asio examples on Windows. The environment variables have no effect on the build output.
Is there a pointer to the Boost.Build docs that describe the use of these variables?
These variables aren't Boost.Build's, they are MSVC-specific, cl.exe uses them. But they are being set by the vcvars32.bat file that b2 calls to set up the cl.exe environment, so any previous values you have will be lost. Things are further complicated by the fact that Boost.Build no longer actually uses Visual Studio's vcvars32.bat file, it generates its own in %TMP%. I looked at tools/build/src/tools/msvc.jam to try to figure out what it does, without much success. So at this point I have no idea how the Asio Jamfile was supposed to work under Windows.