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

http://hadesmem.googlecode.com/ · ReStructuredText · 122 lines · 97 code · 25 blank · 0 comment · 0 complexity · 74b3d4539d805d437638154fce95c68d 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. Install Boost.Build
  5. ...................
  6. Boost.Build_ is a text-based system for developing, testing, and
  7. installing software. First, you'll need to build and
  8. install it. To do this:
  9. 1. Go to the directory ``tools``\ |/|\ ``build``\ |/|\ ``v2``\ |/|.
  10. 2. Run ``bootstrap.bat``
  11. 3. Run ``b2 install --prefix=``\ *PREFIX* where *PREFIX* is
  12. the directory where you want Boost.Build to be installed
  13. 4. Add *PREFIX*\ |/|\ ``bin`` to your PATH environment variable.
  14. .. _Boost.Build: ../../tools/build/index.html
  15. .. _Boost.Build documentation: Boost.Build_
  16. .. _toolset:
  17. .. _toolset-name:
  18. Identify Your Toolset
  19. .....................
  20. First, find the toolset corresponding to your compiler in the
  21. following table (an up-to-date list is always available `in the
  22. Boost.Build documentation`__).
  23. __ http://www.boost.org/boost-build2/doc/html/bbv2/reference/tools.html
  24. .. Note:: If you previously chose a toolset for the purposes of
  25. `building b2`_, you should assume it won't work and instead
  26. choose newly from the table below.
  27. .. _building b2: ../../doc/html/bbv2/installation.html
  28. +-----------+--------------------+-----------------------------+
  29. |Toolset |Vendor |Notes |
  30. |Name | | |
  31. +===========+====================+=============================+
  32. |``acc`` |Hewlett Packard |Only very recent versions are|
  33. | | |known to work well with Boost|
  34. +-----------+--------------------+-----------------------------+
  35. |``borland``|Borland | |
  36. +-----------+--------------------+-----------------------------+
  37. |``como`` |Comeau Computing |Using this toolset may |
  38. | | |require configuring__ another|
  39. | | |toolset to act as its backend|
  40. +-----------+--------------------+-----------------------------+
  41. |``cw`` |Metrowerks/Freescale|The CodeWarrior compiler. We|
  42. | | |have not tested versions of |
  43. | | |this compiler produced since |
  44. | | |it was sold to Freescale. |
  45. +-----------+--------------------+-----------------------------+
  46. |``dmc`` |Digital Mars |As of this Boost release, no |
  47. | | |version of dmc is known to |
  48. | | |handle Boost well. |
  49. +-----------+--------------------+-----------------------------+
  50. |``darwin`` |Apple Computer |Apple's version of the GCC |
  51. | | |toolchain with support for |
  52. | | |Darwin and MacOS X features |
  53. | | |such as frameworks. |
  54. +-----------+--------------------+-----------------------------+
  55. |``gcc`` |The Gnu Project |Includes support for Cygwin |
  56. | | |and MinGW compilers. |
  57. +-----------+--------------------+-----------------------------+
  58. |``hp_cxx`` |Hewlett Packard |Targeted at the Tru64 |
  59. | | |operating system. |
  60. +-----------+--------------------+-----------------------------+
  61. |``intel`` |Intel | |
  62. +-----------+--------------------+-----------------------------+
  63. |``msvc`` |Microsoft | |
  64. +-----------+--------------------+-----------------------------+
  65. |``qcc`` |QNX Software Systems| |
  66. +-----------+--------------------+-----------------------------+
  67. |``sun`` |Sun |Only very recent versions are|
  68. | | |known to work well with |
  69. | | |Boost. |
  70. +-----------+--------------------+-----------------------------+
  71. |``vacpp`` |IBM |The VisualAge C++ compiler. |
  72. +-----------+--------------------+-----------------------------+
  73. __ Boost.Build_
  74. If you have multiple versions of a particular compiler installed,
  75. you can append the version number to the toolset name, preceded by
  76. a hyphen, e.g. ``intel-9.0`` or
  77. ``borland-5.4.3``. |windows-version-name-caveat|
  78. .. _build directory:
  79. .. _build-directory:
  80. Select a Build Directory
  81. ........................
  82. Boost.Build_ will place all intermediate files it generates while
  83. building into the **build directory**. If your Boost root
  84. directory is writable, this step isn't strictly necessary: by
  85. default Boost.Build will create a ``bin.v2/`` subdirectory for that
  86. purpose in your current working directory.
  87. Invoke ``b2``
  88. ...............
  89. .. |build-directory| replace:: *build-directory*
  90. .. |toolset-name| replace:: *toolset-name*
  91. Change your current directory to the Boost root directory and
  92. invoke ``b2`` as follows:
  93. .. parsed-literal::
  94. b2 **--build-dir=**\ |build-directory|_ **toolset=**\ |toolset-name|_ |build-type-complete| stage
  95. For a complete description of these and other invocation options,
  96. please see the `Boost.Build documentation`__.
  97. __ http://www.boost.org/boost-build2/doc/html/bbv2/advanced/invocation.html