/Src/Dependencies/Boost/more/getting_started/detail/header-only.rst

 1.. Copyright David Abrahams 2006. Distributed under the Boost
 2.. Software License, Version 1.0. (See accompanying
 3.. file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
 4
 5Header-Only Libraries
 6=====================
 7
 8The first thing many people want to know is, “how do I build
 9Boost?”  The good news is that often, there's nothing to build.
10
11.. admonition:: Nothing to Build?
12
13  Most Boost libraries are **header-only**: they consist *entirely
14  of header files* containing templates and inline functions, and
15  require no separately-compiled library binaries or special
16  treatment when linking.
17
18.. .. _separate: 
19
20The only Boost libraries that *must* be built separately are:
21
22* Boost.Filesystem_
23* Boost.GraphParallel_
24* Boost.IOStreams_
25* Boost.MPI_
26* Boost.ProgramOptions_
27* Boost.Python_ (see the `Boost.Python build documentation`__
28  before building and installing it)
29* Boost.Regex_
30* Boost.Serialization_
31* Boost.Signals_
32* Boost.System_
33* Boost.Thread_
34* Boost.Wave_
35
36__ ../../libs/python/doc/building.html
37
38A few libraries have optional separately-compiled binaries:
39
40* Boost.DateTime_ has a binary component that is only needed if
41  you're using its ``to_string``\ /\ ``from_string`` or serialization
42  features, or if you're targeting Visual C++ 6.x or Borland.
43
44* Boost.Graph_ also has a binary component that is only needed if
45  you intend to `parse GraphViz files`__.
46
47* Boost.Math_ has binary components for the TR1 and C99
48  cmath functions.
49
50* Boost.Random_ has a binary component which is only needed if
51  you're using ``random_device``.
52
53* Boost.Test_ can be used in “header-only” or “separately compiled”
54  mode, although **separate compilation is recommended for serious
55  use**.
56
57__ ../../libs/graph/doc/read_graphviz.html