虽然Nate的回答已经很好了，但我将根据要求更具体地为Visual Studio 2010展开它，并包括在需要外部库的各种可选组件中编译的信息。

如果您只使用头文件库，那么您所需要做的就是解压缩boost下载并设置环境变量。下面的指令仅为Visual Studio设置环境变量，而不是在整个系统中设置。注意你只需要做一次。

Unarchive the latest version of boost (1.47.0 as of writing) into a directory of your choice (e.g. C:\boost_1_47_0). Create a new empty project in Visual Studio. Open the Property Manager and expand one of the configuration for the platform of your choice. Select & right click Microsoft.Cpp.<Platform>.user, and select Properties to open the Property Page for edit. Select VC++ Directories on the left. Edit the Include Directories section to include the path to your boost source files. Repeat steps 3 - 6 for different platform of your choice if needed.

如果您想使用boost中需要构建的部分，但不需要任何需要外部依赖的特性，那么构建它相当简单。

将最新版本的boost(编写时为1.47.0)解压缩到您选择的目录(例如C:\boost_1_47_0)。 启动所选平台的Visual Studio命令提示符，并导航到boost所在的位置。 运行:bootstrap.bat来构建b2.exe(以前命名为bjam)。 b2运行: Win32: b2——toolset=msvc-10.0——build-type=完成阶段; X64: b2——toolset=msvc-10.0——build-type=完整架构=x86 address-model=64 stage

去散步/看电影或2 / ....

执行上述指令集中的步骤2 - 6来设置环境变量。 编辑库目录部分，以包括到boost库输出的路径。(上面的示例和指令的默认值是C:\boost_1_47_0\stage\lib。如果你想让x86和x64并排(例如到<BOOST_PATH>\lib\x86 & <BOOST_PATH>\lib\x64)，先重命名并移动目录。 重复步骤2 - 6为不同的平台，您的选择，如果需要。

如果您需要可选组件，那么您有更多的工作要做。这些都是:

提振。IOStreams Bzip2过滤器 提振。IOStreams Zlib过滤器 提振。MPI 提振。Python 提振。Regex ICU支持

Boost。IOStreams Bzip2过滤器:

将最新版本的bzip2库(编写时为1.0.6)源文件解压缩到您选择的目录(例如C:\bzip2-1.0.6)。 按照上面的第二组指令构建boost，但是在第5步中运行b2时添加选项-sBZIP2_SOURCE="C:\bzip2-1.0.6"。

提振。IOStreams Zlib过滤器

将最新版本的zlib库(编写时为1.2.5)源文件解压缩到您选择的目录(例如C:\zlib-1.2.5)。 按照上面的第二组指令构建boost，但是在第5步中运行b2时添加选项-sZLIB_SOURCE="C:\zlib-1.2.5"。

提振。MPI

Install a MPI distribution such as Microsoft Compute Cluster Pack. Follow steps 1 - 3 from the second set of instructions above to build boost. Edit the file project-config.jam in the directory <BOOST_PATH> that resulted from running bootstrap. Add in a line that read using mpi ; (note the space before the ';'). Follow the rest of the steps from the second set of instructions above to build boost. If auto-detection of the MPI installation fail, then you'll need to look for and modify the appropriate build file to look for MPI in the right place.

提振。Python

Install a Python distribution such as ActiveState's ActivePython. Make sure the Python installation is in your PATH. To completely built the 32-bits version of the library requires 32-bits Python, and similarly for the 64-bits version. If you have multiple versions installed for such reason, you'll need to tell b2 where to find specific version and when to use which one. One way to do that would be to edit the file project-config.jam in the directory <BOOST_PATH> that resulted from running bootstrap. Add in the following two lines adjusting as appropriate for your Python installation paths & versions (note the space before the ';'). using python : 2.6 : C:\\Python\\Python26\\python ; using python : 2.6 : C:\\Python\\Python26-x64\\python : : : <address-model>64 ; Do note that such explicit Python specification currently cause MPI build to fail. So you'll need to do some separate building with and without specification to build everything if you're building MPI as well. Follow the second set of instructions above to build boost.

提振。Regex ICU支持

Unarchive the latest version of ICU4C library (4.8 as of writing) source file into a directory of your choice (e.g. C:\icu4c-4_8). Open the Visual Studio Solution in <ICU_PATH>\source\allinone. Build All for both debug & release configuration for the platform of your choice. There can be a problem building recent releases of ICU4C with Visual Studio 2010 when the output for both debug & release build are in the same directory (which is the default behaviour). A possible workaround is to do a Build All (of debug build say) and then do a Rebuild all in the 2nd configuration (e.g. release build). If building for x64, you'll need to be running x64 OS as there's post build steps that involves running some of the 64-bits application that it's building. Optionally remove the source directory when you're done. Follow the second set of instructions above to build boost, but add in the option -sICU_PATH="C:\icu4c-4_8" when running b2 in step 5.

你需要Boost的哪些部分?很多东西都是TR1的一部分，它是随Visual Studio一起发布的，所以你可以简单地说，例如:

#include <tr1/memory>

using std::tr1::shared_ptr;

根据James的说法，这也应该工作(在c++ 0x中):

#include <memory>

using std::shared_ptr;

还有一个小提示:如果你想减少编译时间，你可以添加标志

j2

同时运行两个并行构建。这可能会减少到看一部电影;)

这篇文章已经有一段时间了，我想我应该添加一些关于如何在特定的硬件上尽可能快地构建Boost的内容。

如果你有4核或6核，分别使用-j5或-j7。当然不是标准版本，也不是-j2，除非你确实有双核。

我在我的主站上运行了一个3930K(6核)库存的Sandy Bridge Extreme，但在旧的备份盒上有一个2600k(4核)，趋势是我用N + 1构建进程获得了最佳的Boost编译时间，其中N是物理内核的数量。N+2达到收益递减点，时间增加。

注:超线程启用，32GB内存DDR3，三星840 EVO SSD。

-j7在6核(2分51秒)(Win7终极x64)(Visual Studio 2013)

PS C:\Boost\boost_1_56_0> measure-command { .\b2 -j7 --build-type=complete msvc stage }

Days              : 0
Hours             : 0
Minutes           : 2
Seconds           : 51
Milliseconds      : 128
Ticks             : 1711281830
TotalDays         : 0.0019806502662037
TotalHours        : 0.0475356063888889
TotalMinutes      : 2.85213638333333
TotalSeconds      : 171.128183
TotalMilliseconds : 171128.183

-j6在6核(3分2秒)(Win7终极x64)(Visual Studio 2013)

PS C:\Boost\boost_1_56_0> measure-command { .\b2 -j6 --build-type=complete msvc stage }

Days              : 0
Hours             : 0
Minutes           : 3
Seconds           : 2
Milliseconds      : 809
Ticks             : 1828093904
TotalDays         : 0.00211584942592593
TotalHours        : 0.0507803862222222
TotalMinutes      : 3.04682317333333
TotalSeconds      : 182.8093904
TotalMilliseconds : 182809.3904

-j8在6核(3分17秒)(Win7终极x64)(Visual Studio 2013)

PS C:\Boost\boost_1_56_0> measure-command { .\b2 -j8 --build-type=complete msvc stage }

Days              : 0
Hours             : 0
Minutes           : 3
Seconds           : 17
Milliseconds      : 652
Ticks             : 1976523915
TotalDays         : 0.00228764342013889
TotalHours        : 0.0549034420833333
TotalMinutes      : 3.294206525
TotalSeconds      : 197.6523915
TotalMilliseconds : 197652.3915

配置

Building the Boost C++ Libraries.


Performing configuration checks

    - 32-bit                   : yes (cached)
    - arm                      : no  (cached)
    - mips1                    : no  (cached)
    - power                    : no  (cached)
    - sparc                    : no  (cached)
    - x86                      : yes (cached)
    - has_icu builds           : no  (cached)
warning: Graph library does not contain MPI-based parallel components.
note: to enable them, add "using mpi ;" to your user-config.jam
    - zlib                     : no  (cached)
    - iconv (libc)             : no  (cached)
    - iconv (separate)         : no  (cached)
    - icu                      : no  (cached)
    - icu (lib64)              : no  (cached)
    - message-compiler         : yes (cached)
    - compiler-supports-ssse3  : yes (cached)
    - compiler-supports-avx2   : yes (cached)
    - gcc visibility           : no  (cached)
    - long double support      : yes (cached)
warning: skipping optional Message Passing Interface (MPI) library.
note: to enable MPI support, add "using mpi ;" to user-config.jam.
note: to suppress this message, pass "--without-mpi" to bjam.
note: otherwise, you can safely ignore this message.
    - zlib                     : no  (cached)

我注意到64位构建需要更长的时间，我需要对这些进行相同的比较和更新。

此外，还有一些东西我觉得很有用。为您的提升路径使用环境变量。(如何在窗口中设置环境变量，链接在底部7,8,10)BOOST_ROOT变量似乎是常见的地方了，它被设置为解压boost的根路径。

然后在属性，c++，通用，附加包含目录使用$(BOOST_ROOT)。然后，如果/当您移动到boost库的新版本时，您可以更新环境变量以指向这个新版本。随着你的项目越来越多，使用boost，你将不必为所有的项目更新“附加包含目录”。

您还可以创建一个BOOST_LIB变量，并将其指向库暂存的位置。同样地，对于链接器->附加库目录，您不必更新项目。我有一些旧的东西用vs10和vs14建立了新的东西，所以建立了两个口味的boost lib到同一个文件夹。所以如果我把一个项目从vs10移动到vs14，我不需要改变提升路径。

注意:如果你改变了一个环境变量，它不会突然在一个开放VS项目中工作。VS在启动时加载变量。所以你需要关闭VS然后重新打开它。

您还可以尝试-j%NUMBER_OF_PROCESSORS%作为参数，它将使用所有的内核。让我的四核速度超快。