Compile boost libraries windows

The Boost libraries come as source code. While most of the libraries consist solely of header files that can be used directly, some of the libraries require compilation.

In order to make installation as easy as possible, an automated installation process based on Boost. Build is available. Instead of validating and compiling individual libraries separately, Boost. Build installs the complete set automatically. Build can be used with many operating systems and compilers and is able to compile each individual library based on appropriate configuration files.

To automatically install the Boost libraries with Boost. Build , the command-line program bjam is used. The Boost libraries ship this program as source code and not as an executable.

Therefore, two steps are required to build and install the Boost libraries. After you download the Boost libraries, change to the Boost directory and enter the following commands on the command line:.

Enter bootstrap on Windows and. You can stay in Debug mode or change it to Release it won't change anything for our tutorial. Good job, you did it. Anonymous not verified. Thursday, March 26, - pm. Is this tutorial still up to date? I've followed the instructions perfectly as far as I can tell and am getting a whole slew of errors in Visual Studio.

Please let me know if something has changed. Saturday, March 28, - pm. Ronc not verified. Friday, April 10, - pm. Skip to main content. Navigation About. Submitted by Mi-K on Sunday, November 10, - pm.

They contain tons of functionalities but aren't so easy to use or even understand. And test it with Visual Studio and Visual Studio Let's do it in this Boost installation tutorial for Windows First of all We are going to set up our computer in order to use the following libraries and software: Visual Studio feel free to use Visual Studio , more information in this tutorial Boost 1.

Setting up Boost libraries Downloading and installing Boost libraries The Boost libraries are in general available directly without building anything only by including headers. We can include them in our source code without any issues. This is the final step to our journey. The only think we have to do, is to tell the linker to include our binaries. Like before, open the properties window:. Before we proceed take a moment to ensure that the " Configuration " and " Platform " values are selected as shown in the following screenshot.

Note: In case your project builds a static library, the " Linker " menu will be shown as " Librarian ". Recall when we built our targets and created two directories, one for each architecture. This macro defines the correct folder for use depending on the selected build platform. We should now be able to build and run our projects in both x86 and x64 architectures, targeting both debug and release versions. We tried to be as detailed as possible in our explanation.

We wanted to provide a unified reference for future readers who might encounter the same problems we did. As a final note, we inform the readers that we tested all the steps provided in this article, on multiple projects, without any issues. However, if you have a different set-up, that might or might not cause problems. If this is the case, feel free to comment your question or point any ambiguity you have encountered.

I have plans to write more articles regarding project organization and software development in the future. Feel free to post suggestions and articles ideas you might want to read about. Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. David Ortinau - Jan 9. Anubhab Mukherjee - Jan 8.