From: Dean Michael Berris Friday, February 19, 2010 10:41 AM >If Boost.Asio works with any of these, then you should be able to link to them. Fair enough
>Yes. Although the choice of OpenSSL is made by Boost.Asio. Where Boost.Asio works, cpp-netlib should work too. Fair enough > --OpenSSL has a dependency on Perl to build on MS Windows, so an > additional dependency is created (Perl is not packaged with Windows) > > I understand that the effect could be made with a define like > BOOST_NETLIB_NO_SSL, but that seems like a big hammer... Is there no > other way to pay for only what you use (http, in this case)? > >There should be a compile-time option for that, although it's not yet implemented. Boost.Asio has a way of turning off SSL support too. Does this *have* to be a compile-time option? Can't we just not #include some https files?> >Again, if Boost.Asio works with it then it should be doable. >cpp-netlib depends on Boost.Asio to provide the SSL support and functionality at the transport level. cpp-netlib is much higher level for that. Okay, thanks for the detailed response. Erik ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Cpp-netlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel
