That is incorrrect. Boost has binary libraries you link to statically or dynamically depending which parts of boost you use. _Most_ of boost is header only. If you cannot get it to build yourself, it is also distributed as pre built binaries https://sourceforge.net/projects/boost/files/boost-binaries/ and even easier, you can use NuGet to get boost as a nuget package. On Fri, Apr 7, 2017 at 1:55 AM, Sergei Nikulov via Boost-users < boost-users@lists.boost.org> wrote:

2017-04-07 9:38 GMT+03:00 Balázs Bámer via Boost-users :

...

Hi All,

I have downloaded Boost 1.63 the second time. On my home computer, building it yielded all libraries. However, I do similar now at work, and it won't build Asio.

It's header only, AFAIK. So it is nothing to build. _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

Sorry, I was not trying to imply you mix and match, but link to all statically or dynamically. I can't fathom a scenario where you'd want to do some of one and some of the other. You use the preprocessor directive BOOST_ALL_DYN_LINK to dynamically link. -- View this message in context: http://boost.2283326.n4.nabble.com/Boost-Asio-not-built-tp4693482p4693488.ht... Sent from the Boost - Users mailing list archive at Nabble.com.

On 07.04.2017 14:03, Christopher Pisz via Boost-users wrote:

That is incorrrect. Boost has binary libraries you link to statically or dynamically depending which parts of boost you use. _Most_ of boost is header only.

If you cannot get it to build yourself, it is also distributed as pre built binaries https://sourceforge.net/projects/boost/files/boost-binaries/

and even easier, you can use NuGet to get boost as a nuget package.

Boost.Asio is header only unless you don't want it to be. But you have to compile it as a part of your code. There's no precompiled asio library. This is from the Boost.Asio documentation: By default, Boost.Asio is a header-only library. However, some developers may prefer to build Boost.Asio using separately compiled source code. To do this, add|#include|to one (and only one) source file in a program, then build the program with|BOOST_ASIO_SEPARATE_COMPILATION|defined in the project/compiler settings. Alternatively,|BOOST_ASIO_DYN_LINK|may be defined to build a separately-compiled Boost.Asio as part of a shared library. If using Boost.Asio's SSL support, you will also need to add|#include|. Cheers, Leon

On Fri, Apr 7, 2017 at 1:55 AM, Sergei Nikulov via Boost-users mailto:boost-users@lists.boost.org> wrote:

2017-04-07 9:38 GMT+03:00 Balázs Bámer via Boost-users mailto:boost-users@lists.boost.org>: > Hi All, > > I have downloaded Boost 1.63 the second time. On my home computer, building > it yielded all libraries. However, I do similar now at work, and it won't > build Asio. >

It's header only, AFAIK. So it is nothing to build. _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org mailto:Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users http://lists.boost.org/mailman/listinfo.cgi/boost-users

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users