This section describes how to install Boost.Build from a
All paths are given relative to
the Boost.Build v2 root directory, which is
located in the
of a full Boost distribution.
To install Boost.Jam, copy the executable,
or bjam.exe to a location accessible in
PATH. Go to the Boost.Build root
Boost.Build V2 (Milestone N) Boost.Jam xx.xx.xx
where N is the version of Boost.Build you're using.
user-config.jamfile in the Boost.Build root directory and follow the instructions there to describe your toolsets and libraries, and, if necessary, where they are located.
example/hello/directory and run bjam there. A simple application will be built. You can also play with other projects in the
If you are using Boost's CVS state, be sure to rebuild bjam even if you have a previous version. The CVS version of Boost.Build requires the CVS version of Boost.Jam.
When bjam is invoked, it always needs to be able to find the Boost.Build root directory, where the interpreted source code of Boost.Build is located. There are two ways to tell bjam about the root directory:
BOOST_BUILD_PATHto the absolute path of the Boost.Build root directory.
At the root directory of your project or in any of its
parent directories, create a file called
boost-build.jam, with a single line:
If you're planning to package Boost.Build for a Linux distribution, please follow these guidelines:
Create a separate package for Boost.Jam.
Create another package for Boost.Build, and make
this package install all Boost.Build files to
/usr/share/boost-build directory. After
install, that directory should contain everything you see in
Boost.Build release package, except for
jam_src directory. If you're using Boost CVS
to obtain Boost.Build, as opposed to release package, take
everything from the
For a check, make sure that
/usr/share/boost-build/boost-build.jam is installed.
Placing Boost.Build into
will make sure that bjam will find Boost.Build
without any additional setup.
/etc/site-config.jam configuration file that will
using gcc ;
You might want to add dependency from Boost.Build package to gcc, to make sure that users can always build Boost.Build examples.
If those guidelines are met, users will be able to invoke bjam without any explicit configuration.
 Note that packages prepared for Unix/Linux systems usually make their own choices about where to put things and even which parts of Boost to include. When we say “released source distribution” we mean a distribution of Boost as released on its SourceForge project page.
 The Boost.Build subset of boost is also distributed
separately, for those who are only interested in getting a
build tool. The top-level directory of a Boost.Build
distribution contains all the subdirectories of the
tools/build/v2 subdirectory from a full
Boost distribution, so it is itself a valid Boost.Build root
directory. It also contains the
tools/jam/src subdirectory of a
full Boost distribution, so you can rebuild Boost.Jam from