PageRenderTime 22ms CodeModel.GetById 14ms app.highlight 5ms RepoModel.GetById 1ms app.codeStats 0ms

/Src/Dependencies/Boost/more/getting_started/detail/build-from-source-tail.rst

http://hadesmem.googlecode.com/
ReStructuredText | 73 lines | 53 code | 20 blank | 0 comment | 0 complexity | 515026aade6f3728565eec01853fe5cc MD5 | raw file
 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
 5Building the special ``stage`` target places Boost
 6library binaries in the ``stage``\ |/|\ ``lib``\ |/| subdirectory of
 7the Boost tree.  To use a different directory pass the
 8``--stagedir=``\ *directory* option to ``b2``.
 9
10.. Note:: ``b2`` is case-sensitive; it is important that all the
11   parts shown in **bold** type above be entirely lower-case.
12
13For a description of other options you can pass when invoking
14``b2``, type::
15
16  b2 --help
17
18In particular, to limit the amount of time spent building, you may
19be interested in:
20
21* reviewing the list of library names with ``--show-libraries``
22* limiting which libraries get built with the ``--with-``\
23  *library-name* or ``--without-``\ *library-name* options
24* choosing a specific build variant by adding ``release`` or
25  ``debug`` to the command line.
26
27.. Note:: Boost.Build can produce a great deal of output, which can
28     make it easy to miss problems.  If you want to make sure
29     everything is went well, you might redirect the output into a
30     file by appending “``>build.log 2>&1``” to your command line.
31
32Expected Build Output
33---------------------
34
35During the process of building Boost libraries, you can expect to
36see some messages printed on the console.  These may include
37
38* Notices about Boost library configuration—for example, the Regex
39  library outputs a message about ICU when built without Unicode
40  support, and the Python library may be skipped without error (but
41  with a notice) if you don't have Python installed.
42
43* Messages from the build tool that report the number of targets
44  that were built or skipped.  Don't be surprised if those numbers
45  don't make any sense to you; there are many targets per library.
46
47* Build action messages describing what the tool is doing, which
48  look something like:
49
50  .. parsed-literal::
51
52    *toolset-name*.c++ *long*\ /\ *path*\ /\ *to*\ /\ *file*\ /\ *being*\ /\ *built*
53
54* Compiler warnings.
55
56In Case of Build Errors
57-----------------------
58
59The only error messages you see when building Boost—if any—should
60be related to the IOStreams library's support of zip and bzip2
61formats as described here__.  Install the relevant development
62packages for libz and libbz2 if you need those features.  Other
63errors when building Boost libraries are cause for concern.
64
65__ ../../libs/iostreams/doc/installation.html
66
67If it seems like the build system can't find your compiler and/or
68linker, consider setting up a ``user-config.jam`` file as described
69`here`__.  If that isn't your problem or the ``user-config.jam`` file
70doesn't work for you, please address questions about configuring Boost
71for your compiler to the `Boost.Build mailing list`_.
72
73__ http://www.boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html