summaryrefslogtreecommitdiff
path: root/doc/html/bbv2/overview.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/bbv2/overview.html')
-rw-r--r--[-rwxr-xr-x]doc/html/bbv2/overview.html214
1 files changed, 106 insertions, 108 deletions
diff --git a/doc/html/bbv2/overview.html b/doc/html/bbv2/overview.html
index 3bce75193a..89e5f54953 100755..100644
--- a/doc/html/bbv2/overview.html
+++ b/doc/html/bbv2/overview.html
@@ -44,17 +44,17 @@
Boost.Build actually consists of two parts - Boost.Jam, a build engine
with its own interpreted language, and Boost.Build itself, implemented in
Boost.Jam's language. The chain of events when you type
- <span class="command"><strong>bjam</strong></span> on the command line is as follows:
+ <span class="command"><strong>b2</strong></span> on the command line is as follows:
</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem"><p>
- Boost.Jam tries to find Boost.Build and loads the top-level module.
- The exact process is described in <a class="xref" href="reference.html#bbv2.reference.init" title="Initialization">the section called &#8220;Initialization&#8221;</a>
+ The Boost.Build executable tries to find Boost.Build modules and
+ loads the top-level module. The exact process is described in <a class="xref" href="reference.html#bbv2.reference.init" title="Initialization">the section called &#8220;Initialization&#8221;</a>
</p></li>
<li class="listitem"><p>
The top-level module loads user-defined configuration files,
- <code class="filename">user-config.jam</code> and <code class="filename">site-config.jam
- </code>, which define available toolsets.
+ <code class="filename">user-config.jam</code> and
+ <code class="filename">site-config.jam</code>, which define available toolsets.
</p></li>
<li class="listitem"><p>
The Jamfile in the current directory is read. That in turn might
@@ -109,8 +109,8 @@ a.o: a.c
g++ -o a.o -g a.c
</pre>
<p>
- This is rather low-level description mechanism and it's hard to adjust commands, options,
- and sets of created targets depending on the used compiler and operating system.
+ This is a rather low-level description mechanism and it's hard to adjust commands, options,
+ and sets of created targets depending on the compiler and operating system used.
</p>
<p>
To improve portability, most modern build system provide a set of higher-level
@@ -120,19 +120,19 @@ a.o: a.c
add_program ("a", "a.c")
</pre>
<p>
- This is a function call that creates targets necessary to create executable file
- from source file <code class="filename">a.c</code>. Depending on configured properties,
- different commands line may be used. However, <code class="computeroutput">add_program</code> is higher-level,
- but rather thin level. All targets are created immediately when build description
+ This is a function call that creates the targets necessary to create a executable file
+ from the source file <code class="filename">a.c</code>. Depending on configured properties,
+ different command lines may be used. However, <code class="computeroutput">add_program</code> is higher-level,
+ but rather thin level. All targets are created immediately when the build description
is parsed, which makes it impossible to perform multi-variant builds. Often, change
- in any build property requires complete reconfiguration of the build tree.
+ in any build property requires a complete reconfiguration of the build tree.
</p>
<p>
- In order to support true multivariant builds, Boost.Build introduces the concept of
- <a class="indexterm" name="id3894430"></a>
- <a class="indexterm" name="id3894441"></a>
- <em class="firstterm">metatarget</em>&#8212;object that is created when build description
- is parsed and can be later called with specific build properties to generate
+ In order to support true multivariant builds, Boost.Build introduces the concept of a
+ <a class="indexterm" name="id3994348"></a>
+ <a class="indexterm" name="id3994361"></a>
+ <em class="firstterm">metatarget</em>&#8212;an object that is created when the build description
+ is parsed and can be called later with specific build properties to generate
actual targets.
</p>
<p>
@@ -143,12 +143,12 @@ exe a : a.cpp ;
</pre>
<p>
When this declaration is parsed, Boost.Build creates a metatarget, but does not
- yet decides what files must be created, or what commands must be used. After
- all build files are parsed, Boost.Build considers properties requested on the
+ yet decide what files must be created, or what commands must be used. After
+ all build files are parsed, Boost.Build considers the properties requested on the
command line. Supposed you have invoked Boost.Build with:
</p>
<pre class="screen">
-bjam toolset=gcc toolset=msvc
+b2 toolset=gcc toolset=msvc
</pre>
<p>
In that case, the metatarget will be called twice, once with <code class="computeroutput">toolset=gcc</code>
@@ -156,26 +156,26 @@ bjam toolset=gcc toolset=msvc
targets, that will have different extensions and use different command lines.
</p>
<p>
- Another key concept is
- <a class="indexterm" name="id3894500"></a>
- <em class="firstterm">build property</em>. Build property is a variable
+ Another key concept is
+ <a class="indexterm" name="id3994420"></a>
+ <em class="firstterm">build property</em>. A build property is a variable
that affects the build process. It can be specified on the command line, and is
passed when calling a metatarget. While all build tools have a similar mechanism,
Boost.Build differs by requiring that all build properties are declared in advance,
and providing a large set of properties with portable semantics.
</p>
<p>
- The final concept is <a class="indexterm" name="id3894523"></a>
+ The final concept is <a class="indexterm" name="id3994442"></a>
<em class="firstterm">property propagation</em>. Boost.Build does not require that every
metatarget is called with the same properties. Instead, the
"top-level" metatargets are called with the properties specified on the command line.
Each metatarget can elect to augment or override some properties (in particular,
using the requirements mechanism, see <a class="xref" href="overview.html#bbv2.overview.targets.requirements" title="Requirements">the section called &#8220;Requirements&#8221;</a>).
- Then, the dependency metatargets are called with modified properties and produce
- concrete targets that are then used in build process. Of course, dependency metatargets
+ Then, the dependency metatargets are called with the modified properties and produce
+ concrete targets that are then used in the build process. Of course, dependency metatargets
maybe in turn modify build properties and have dependencies of their own.
</p>
-<p>For more in-depth treatment of the requirements and concepts, you may refer
+<p>For a more in-depth treatment of the requirements and concepts, you may refer
to <a href="http://syrcose.ispras.ru/2009/files/04_paper.pdf" target="_top">SYRCoSE 2009 Boost.Build article</a>.
</p>
</div>
@@ -183,15 +183,15 @@ bjam toolset=gcc toolset=msvc
<div class="titlepage"><div><div><h3 class="title">
<a name="bbv2.overview.jam_language"></a>Boost.Jam Language</h3></div></div></div>
<p>
- This section will describe the basics of the Boost.Jam language&#8212;
- just enough for writing Jamfiles. For more information, please see the
+ This section will describe the basics of the Boost.Jam language&#8212;just
+ enough for writing Jamfiles. For more information, please see the
<a class="link" href="../">Boost.Jam</a> documentation.
</p>
<p>
<a class="link" href="../">Boost.Jam</a> has an interpreted, procedural
language. On the lowest level, a <a class="link" href="../">Boost.Jam
- </a> program consists of variables and <a class="indexterm" name="id3894614"></a> <em class="firstterm">rules</em> (Jam term for
- function). They are grouped into modules&#8212;there is one global
+ </a> program consists of variables and <a class="indexterm" name="id3994534"></a> <em class="firstterm">rules</em> (the Jam term for
+ functions). They are grouped into modules&#8212;there is one global
module and a number of named modules. Besides that, a <a class="link" href="../">Boost.Jam</a> program contains classes and class
instances.
</p>
@@ -358,15 +358,15 @@ import <em class="replaceable"><code>module</code></em> ;
import <em class="replaceable"><code>module</code></em> : <em class="replaceable"><code>rule</code></em> ;
</pre>
<p>
- The first form imports the specified bjam module. All rules from that
+ The first form imports the specified module. All rules from that
module are made available using the qualified name: <code class="computeroutput"><em class="replaceable"><code>
module</code></em>.<em class="replaceable"><code>rule</code></em></code>. The second
form imports the specified rules only, and they can be called using
unqualified names.
</p>
<p><a name="bbv2.overview.jam_language.actions"></a>
- Sometimes, you'd need to specify the actual command lines to be used
- when creating targets. In jam language, you use named actions to do
+ Sometimes, you need to specify the actual command lines to be used
+ when creating targets. In the jam language, you use named actions to do
this. For example:
</p>
<pre class="programlisting">
@@ -383,8 +383,8 @@ actions create-file-from-another
</code> variable will be expanded to a list of source files.
</p>
<p>
- To flexibly adjust the command line, you can define a rule with the same
- name as the action and taking three parameters -- targets, sources and
+ To adjust the command line flexibly, you can define a rule with the same
+ name as the action and taking three parameters&#8212;targets, sources and
properties. For example:
</p>
<pre class="programlisting">
@@ -401,15 +401,15 @@ actions create-file-from-another
}
</pre>
<p>
- In this example, the rule checks if certain build property is specified.
- If so, it sets variable <code class="varname">OPIONS</code> that is then used
+ In this example, the rule checks if a certain build property is specified.
+ If so, it sets the variable <code class="varname">OPIONS</code> that is then used
inside the action. Note that the variables set "on a target" will be
visible only inside actions building that target, not globally. Were
they set globally, using variable named <code class="varname">OPTIONS</code> in
two unrelated actions would be impossible.
</p>
<p>
- More details can be found in Jam reference, <a class="xref" href="../jam/language.html#jam.language.rules" title="Rules">the section called &#8220;Rules&#8221;</a>.
+ More details can be found in the Jam reference, <a class="xref" href="../jam/language.html#jam.language.rules" title="Rules">the section called &#8220;Rules&#8221;</a>.
</p>
</div>
<div class="section">
@@ -418,9 +418,9 @@ actions create-file-from-another
<p>
On startup, Boost.Build searches and reads two configuration files:
<code class="filename">site-config.jam</code> and <code class="filename">user-config.jam</code>.
- The first one is usually installed and maintained by system administrator, and
- the second is for user to modify. You can edit the one in the top-level
- directory of Boost.Build installation or create a copy in your home
+ The first one is usually installed and maintained by a system administrator, and
+ the second is for the user to modify. You can edit the one in the top-level
+ directory of your Boost.Build installation or create a copy in your home
directory and edit the copy. The following table explains where both files
are searched.
</p>
@@ -478,7 +478,7 @@ actions create-file-from-another
</p></td></tr>
</table></div>
<p>
- Usually, <code class="filename">user-config.jam</code> just defines available compilers
+ Usually, <code class="filename">user-config.jam</code> just defines the available compilers
and other tools (see <a class="xref" href="faq.html#bbv2.recipies.site-config" title="Targets in site-config.jam">the section called &#8220;Targets in site-config.jam&#8221;</a> for more advanced
usage). A tool is configured using the following syntax:
</p>
@@ -486,7 +486,7 @@ actions create-file-from-another
using <em class="replaceable"><code>tool-name</code></em> : ... ;
</pre>
<p>
- The <code class="computeroutput">using</code> rule is given a name of tool, and
+ The <code class="computeroutput">using</code> rule is given the name of tool, and
will make that tool available to Boost.Build. For example,
</p>
<pre class="programlisting">
@@ -500,7 +500,7 @@ using gcc ;
C++ compilers are below.
</p>
<p>
- For all the C++ compiler toolsets Boost.Build supports
+ For all the C++ compiler toolsets that Boost.Build supports
out-of-the-box, the list of parameters to
<code class="computeroutput">using</code> is the same: <em class="parameter"><code>toolset-name</code></em>, <em class="parameter"><code>version</code></em>, <em class="parameter"><code>invocation-command</code></em>, and <em class="parameter"><code>options</code></em>.
</p>
@@ -528,8 +528,8 @@ using msvc : : "Z:/Programs/Microsoft Visual Studio/vc98/bin/cl" ;
<p>
Some Boost.Build toolsets will use that path to take additional actions
required before invoking the compiler, such as calling vendor-supplied
- scripts to set up its required environment variables. When compiler
- executables for C and C++ are different, path to the C++ compiler
+ scripts to set up its required environment variables. When the compiler
+ executables for C and C++ are different, the path to the C++ compiler
executable must be specified. The command can
be any command allowed by the operating system. For example:
</p>
@@ -594,16 +594,16 @@ using gcc : 3.2 : g++-3.2 ;
<dt><span class="section"><a href="overview.html#bbv2.overview.invocation.properties">Properties</a></span></dt>
<dt><span class="section"><a href="overview.html#bbv2.overview.invocation.targets">Targets</a></span></dt>
</dl></div>
-<p>To invoke Boost.Build, type <span class="command"><strong>bjam</strong></span> on the command line. Three kinds
+<p>To invoke Boost.Build, type <span class="command"><strong>b2</strong></span> on the command line. Three kinds
of command-line tokens are accepted, in any order:</p>
<div class="variablelist"><dl>
<dt><span class="term">options</span></dt>
-<dd><p>Options start with either dash, or two dashes. The standard options
+<dd><p>Options start with either one or two dashes. The standard options
are listed below, and each project may add additional options</p></dd>
<dt><span class="term">properties</span></dt>
<dd><p>Properties specify details of what you want to build (e.g. debug
- or release variant). Syntactically, all command line tokens with equal sign in them
- are considered to specify properties. In the simplest form, property looks like
+ or release variant). Syntactically, all command line tokens with an equal sign in them
+ are considered to specify properties. In the simplest form, a property looks like
<span class="command"><strong><em class="replaceable"><code>feature</code></em>=<em class="replaceable"><code>value</code></em></strong></span>
</p></dd>
<dt><span class="term">target</span></dt>
@@ -614,17 +614,17 @@ using gcc : 3.2 : g++-3.2 ;
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="bbv2.overview.invocation.examples"></a>Examples</h4></div></div></div>
-<p>To build all targets defined in Jamfile in the current directory with default properties, run:
+<p>To build all targets defined in the Jamfile in the current directory with the default properties, run:
</p>
<pre class="screen">
-bjam
+b2
</pre>
<p>
</p>
<p>To build specific targets, specify them on the command line:
</p>
<pre class="screen">
-bjam lib1 subproject//lib2
+b2 lib1 subproject//lib2
</pre>
<p>
</p>
@@ -632,7 +632,7 @@ bjam lib1 subproject//lib2
<em class="replaceable"><code>property</code></em>=<em class="replaceable"><code>value</code></em></code> to the command line:
</p>
<pre class="screen">
-bjam toolset=gcc variant=debug optimization=space
+b2 toolset=gcc variant=debug optimization=space
</pre>
<p>
</p>
@@ -661,8 +661,8 @@ bjam toolset=gcc variant=debug optimization=space
</p></dd>
<dt><span class="term"><code class="option">--build-dir</code></span></dt>
<dd>
-<p>Changes build directories for all project roots being built. When
- this option is specified, all Jamroot files should declare project name.
+<p>Changes the build directories for all project roots being built. When
+ this option is specified, all Jamroot files must declare a project name.
The build directory for the project root will be computed by concatanating
the value of the <code class="option">--build-dir</code> option, the project name
specified in Jamroot, and the build dir specified in Jamroot
@@ -673,7 +673,7 @@ bjam toolset=gcc variant=debug optimization=space
</p>
</dd>
<dt><span class="term"><code class="option">--version</code></span></dt>
-<dd><p>Prints information on Boost.Build and Boost.Jam
+<dd><p>Prints information on the Boost.Build and Boost.Jam
versions.
</p></dd>
<dt><span class="term"><code class="option">-a</code></span></dt>
@@ -681,23 +681,23 @@ bjam toolset=gcc variant=debug optimization=space
<dt><span class="term"><code class="option">-n</code></span></dt>
<dd><p>Do no execute the commands, only print them.</p></dd>
<dt><span class="term"><code class="option">-q</code></span></dt>
-<dd><p>Stop at first error, as opposed to continuing to build targets
+<dd><p>Stop at the first error, as opposed to continuing to build targets
that don't depend on the failed ones.</p></dd>
<dt><span class="term"><code class="option">-j <em class="replaceable"><code>N</code></em></code></span></dt>
<dd><p>Run up to <em class="replaceable"><code>N</code></em> commands in parallel.</p></dd>
<dt><span class="term"><code class="option">--debug-configuration</code></span></dt>
-<dd><p>Produces debug information about loading of Boost.Build
+<dd><p>Produces debug information about the loading of Boost.Build
and toolset files.</p></dd>
<dt><span class="term"><code class="option">--debug-building</code></span></dt>
<dd><p>Prints what targets are being built and with what properties.
</p></dd>
<dt><span class="term"><code class="option">--debug-generators</code></span></dt>
-<dd><p>Produces debug output from generator search process.
+<dd><p>Produces debug output from the generator search process.
Useful for debugging custom generators.
</p></dd>
<dt><span class="term"><code class="option">--ignore-config</code></span></dt>
-<dd><p>Do not load <code class="literal">site-config.jam</code> and
- <code class="literal">user-config.jam</code> configuration files.
+<dd><p>Do not load <code class="literal">site-config.jam</code> or
+ <code class="literal">user-config.jam</code>.
</p></dd>
<dt><span class="term"><code class="option">-d0</code></span></dt>
<dd><p>Supress all informational messages.</p></dd>
@@ -745,7 +745,7 @@ bjam toolset=gcc variant=debug optimization=space
The complete list of features can be found in <a class="xref" href="reference.html#bbv2.overview.builtins.features" title="Builtin features">the section called &#8220;Builtin features&#8221;</a>.
The most common features are summarized below.</p>
<div class="table">
-<a name="id3896181"></a><p class="title"><b>Table&#160;39.2.&#160;</b></p>
+<a name="id3996105"></a><p class="title"><b>Table&#160;39.2.&#160;</b></p>
<div class="table-contents"><table class="table">
<colgroup>
<col>
@@ -821,37 +821,34 @@ bjam toolset=gcc variant=debug optimization=space
</tbody>
</table></div>
</div>
-<br class="table-break">
-
- If you have more than one version of a given C++ toolset (e.g. configured in
+<br class="table-break"><p>If you have more than one version of a given C++ toolset (e.g. configured in
<code class="filename">user-config.jam</code>, or autodetected, as happens with msvc), you can
request the specific version by passing
<code class="computeroutput"><em class="replaceable"><code>toolset</code></em>-<em class="replaceable"><code>version</code></em></code> as
the value of the <code class="computeroutput">toolset</code> feature, for example <code class="computeroutput">toolset=msvc-8.0</code>.
-
-
- <p>
+ </p>
+<p>
If a feature has a fixed set of values it can be specified more than
once on the command line.
In which case, everything will be built several times --
once for each specified value of a feature. For example, if you use
</p>
<pre class="screen">
-bjam link=static link=shared threading=single threading=multi
+b2 link=static link=shared threading=single threading=multi
</pre>
<p>
Then a total of 4 builds will be performed. For convenience,
instead of specifying all requested values of a feature in separate command line elements,
- you can separate the values with commands, for example:
+ you can separate the values with commas, for example:
</p>
<pre class="screen">
-bjam link=static,shared threading=single,multi
+b2 link=static,shared threading=single,multi
</pre>
<p>
- The comma has special meaning only if the feature has a fixed set of values, so
+ The comma has this special meaning only if the feature has a fixed set of values, so
</p>
<pre class="screen">
-bjam include=static,shared
+b2 include=static,shared
</pre>
<p>is not treated specially.</p>
</div>
@@ -867,11 +864,11 @@ bjam include=static,shared
<div class="titlepage"><div><div><h3 class="title">
<a name="bbv2.overview.targets"></a>Declaring Targets</h3></div></div></div>
<div class="toc"><dl>
-<dt><span class="section"><a href="overview.html#id3896594">Name</a></span></dt>
-<dt><span class="section"><a href="overview.html#id3896750">Sources</a></span></dt>
+<dt><span class="section"><a href="overview.html#id3996520">Name</a></span></dt>
+<dt><span class="section"><a href="overview.html#id3996676">Sources</a></span></dt>
<dt><span class="section"><a href="overview.html#bbv2.overview.targets.requirements">Requirements</a></span></dt>
-<dt><span class="section"><a href="overview.html#id3897336">Default Build</a></span></dt>
-<dt><span class="section"><a href="overview.html#id3897364">Additional Information</a></span></dt>
+<dt><span class="section"><a href="overview.html#id3996995">Default Build</a></span></dt>
+<dt><span class="section"><a href="overview.html#id3997023">Additional Information</a></span></dt>
</dl></div>
<p><a name="bbv2.overview.targets.main"></a>
A <em class="firstterm">Main target</em> is a user-defined named
@@ -880,9 +877,9 @@ bjam include=static,shared
target rules described in <a class="xref" href="reference.html#bbv2.reference.rules" title="Builtin rules">the section called &#8220;Builtin rules&#8221;</a>. The user can also declare
custom main target rules as shown in <a class="xref" href="extender.html#bbv2.extending.rules" title="Main target rules">the section called &#8220;Main target rules&#8221;</a>.
</p>
-<a class="indexterm" name="id3896541"></a><p>Most main target rules in Boost.Build have the same common
+<a class="indexterm" name="id3996468"></a><p>Most main target rules in Boost.Build have the same common
signature:</p>
-<a class="indexterm" name="id3896555"></a><a name="bbv2.main-target-rule-syntax"></a><pre class="programlisting">
+<a class="indexterm" name="id3996481"></a><a name="bbv2.main-target-rule-syntax"></a><pre class="programlisting">
rule <em class="replaceable"><code>rule-name</code></em> (
main-target-name :
sources + :
@@ -923,14 +920,14 @@ rule <em class="replaceable"><code>rule-name</code></em> (
stated in their documentation.
</p>
<p>The actual requirements for a target are obtained by refining
- requirements of the project where a target is declared with the
+ the requirements of the project where the target is declared with the
explicitly specified requirements. The same is true for
usage-requirements. More details can be found in
<a class="xref" href="reference.html#bbv2.reference.variants.proprefine" title="Property refinement">the section called &#8220;Property refinement&#8221;</a>
</p>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id3896594"></a>Name</h4></div></div></div>
+<a name="id3996520"></a>Name</h4></div></div></div>
<p>The name of main target has two purposes. First, it's used to refer to this target from
other targets and from command line. Second, it's used to compute the names of the generated files.
Typically, filenames are obtained from main target name by appending system-dependent suffixes and
@@ -950,13 +947,14 @@ obj test.debug : test.cpp : &lt;variant&gt;debug ;
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id3896750"></a>Sources</h4></div></div></div>
+<a name="id3996676"></a>Sources</h4></div></div></div>
<p>The list of sources specifies what should be processed to
get the resulting targets. Most of the time, it's just a list of
files. Sometimes, you'll want to automatically construct the
list of source files rather than having to spell it out
manually, in which case you can use the
- <code class="computeroutput">glob</code> rule. Here are two examples:</p>
+ <a class="link" href="reference.html#bbv2.reference.rules.glob">glob</a> rule.
+ Here are two examples:</p>
<pre class="programlisting">
exe a : a.cpp ; # a.cpp is the only source file
exe b : [ glob *.cpp ] ; # all .cpp files in this directory are sources
@@ -996,14 +994,14 @@ exe c : c.cpp /boost/program_options//program_options ;
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="bbv2.overview.targets.requirements"></a>Requirements</h4></div></div></div>
-<a class="indexterm" name="id3896849"></a><p>Requirements are the properties that should always be present when
+<a class="indexterm" name="id3996778"></a><p>Requirements are the properties that should always be present when
building a target. Typically, they are includes and defines:
</p>
<pre class="programlisting">
exe hello : hello.cpp : &lt;include&gt;/opt/boost &lt;define&gt;MY_DEBUG ;
</pre>
<p>
- There is a number of other features, listed in
+ There are a number of other features, listed in
<a class="xref" href="reference.html#bbv2.overview.builtins.features" title="Builtin features">the section called &#8220;Builtin features&#8221;</a>. For example if
a library can only be built statically, or a file can't be compiled
with optimization due to a compiler bug, one can use
@@ -1070,15 +1068,15 @@ rule my-rule ( properties * )
</p>
<p>Requirements explicitly specified for a target are usually
combined with the requirements specified for the containing project. You
- can cause a target to completely ignore specific project's requirement
- using the syntax by adding a minus sign before a property, for example:
+ can cause a target to completely ignore a specific project requirement
+ using the syntax by adding a minus sign before the property, for example:
</p>
<pre class="programlisting">
exe main : main.cpp : <span class="bold"><strong>-&lt;define&gt;UNNECESSARY_DEFINE</strong></span> ;
</pre>
<p>
- This syntax is the only way to ignore free properties from a parent,
- such as defines. It can be also useful for ordinary properties. Consider
+ This syntax is the only way to ignore free properties, such as defines,
+ from a parent. It can be also useful for ordinary properties. Consider
this example:
</p>
<pre class="programlisting">
@@ -1088,12 +1086,12 @@ exe test2 : test2.cpp : &lt;threading&gt;single ;
exe test3 : test3.cpp : -&lt;threading&gt;multi ;
</pre>
<p>
- Here, <code class="computeroutput">test1</code> inherits project requirements and will always
+ Here, <code class="computeroutput">test1</code> inherits the project requirements and will always
be built in multi-threaded mode. The <code class="computeroutput">test2</code> target
- <span class="emphasis"><em>overrides</em></span> project's requirements and will
+ <span class="emphasis"><em>overrides</em></span> the project's requirements and will
always be built in single-threaded mode. In contrast, the
<code class="computeroutput">test3</code> target <span class="emphasis"><em>removes</em></span> a property
- from project requirements and will be built either in single-threaded or
+ from the project requirements and will be built either in single-threaded or
multi-threaded mode depending on which variant is requested by the
user.</p>
<p>Note that the removal of requirements is completely textual:
@@ -1101,7 +1099,7 @@ exe test3 : test3.cpp : -&lt;threading&gt;multi ;
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id3897336"></a>Default Build</h4></div></div></div>
+<a name="id3996995"></a>Default Build</h4></div></div></div>
<p>The <code class="varname">default-build</code> parameter
is a set of properties to be used if the build request does
not otherwise specify a value for features in the set. For example:
@@ -1112,13 +1110,13 @@ exe hello : hello.cpp : : &lt;threading&gt;multi ;
<p>
would build a multi-threaded target unless the user
explicitly requests a single-threaded version. The difference between
- requirements and default-build is that requirements cannot be
+ the requirements and the default-build is that the requirements cannot be
overridden in any way.
</p>
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id3897364"></a>Additional Information</h4></div></div></div>
+<a name="id3997023"></a>Additional Information</h4></div></div></div>
<p>
The ways a target is built can be so different that
describing them using conditional requirements would be
@@ -1128,7 +1126,7 @@ exe hello : hello.cpp : : &lt;threading&gt;multi ;
alternatives</em>:
</p>
<pre class="programlisting">
-lib demangler : dummy_demangler.cpp ; # alternative 1
+lib demangler : dummy_demangler.cpp ; # alternative 1
lib demangler : demangler_gcc.cpp : &lt;toolset&gt;gcc ; # alternative 2
lib demangler : demangler_msvc.cpp : &lt;toolset&gt;msvc ; # alternative 3
</pre>
@@ -1149,12 +1147,12 @@ exe hello : hello.cpp
optimization. When referring to an inline main target, its declared
name must be prefixed by its parent target's name and two dots. In
the example above, to build only helpers, one should run
- <code class="computeroutput">bjam hello..helpers</code>.
+ <code class="computeroutput">b2 hello..helpers</code>.
</p>
<p>When no target is requested on the command line, all targets in the
current project will be built. If a target should be built only by
explicit request, this can be expressed by the
- <code class="computeroutput">explicit</code> rule:
+ <a class="link" href="reference.html#bbv2.reference.rules.explicit">explicit</a> rule:
</p>
<pre class="programlisting">
explicit install_programs ;</pre>
@@ -1211,7 +1209,7 @@ project tennis
</p>
<div class="table">
-<a name="id3897577"></a><p class="title"><b>Table&#160;39.3.&#160;</b></p>
+<a name="id3997240"></a><p class="title"><b>Table&#160;39.3.&#160;</b></p>
<div class="table-contents"><table class="table" summary="">
<colgroup>
<col>
@@ -1312,8 +1310,8 @@ project tennis
<a name="bbv2.overview.build_process"></a>The Build Process</h3></div></div></div>
<div class="toc"><dl>
<dt><span class="section"><a href="overview.html#bbv2.overview.build_request">Build Request</a></span></dt>
-<dt><span class="section"><a href="overview.html#id3897894">Building a main target</a></span></dt>
-<dt><span class="section"><a href="overview.html#id3898010">Building a Project</a></span></dt>
+<dt><span class="section"><a href="overview.html#id3997557">Building a main target</a></span></dt>
+<dt><span class="section"><a href="overview.html#id3997672">Building a Project</a></span></dt>
</dl></div>
<p>When you've described your targets, you want Boost.Build to run the
right tools and create the needed targets.
@@ -1351,7 +1349,7 @@ project tennis
properties. For example:
</p>
<pre class="programlisting">
-bjam app1 lib1//lib1 toolset=gcc variant=debug optimization=full
+b2 app1 lib1//lib1 toolset=gcc variant=debug optimization=full
</pre>
<p>
would build two targets, "app1" and "lib1//lib1" with the specified
@@ -1361,7 +1359,7 @@ bjam app1 lib1//lib1 toolset=gcc variant=debug optimization=full
of the property can be omitted. For example, the above can be written as:
</p>
<pre class="programlisting">
-bjam app1 lib1//lib1 gcc debug optimization=full
+b2 app1 lib1//lib1 gcc debug optimization=full
</pre>
<p>
The complete syntax, which has some additional shortcuts, is
@@ -1370,7 +1368,7 @@ bjam app1 lib1//lib1 gcc debug optimization=full
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id3897894"></a>Building a main target</h4></div></div></div>
+<a name="id3997557"></a>Building a main target</h4></div></div></div>
<p>When you request, directly or indirectly, a build of a main target
with specific requirements, the following steps are done. Some brief
explanation is provided, and more details are given in <a class="xref" href="reference.html#bbv2.reference.buildprocess" title="Build process">the section called &#8220;Build process&#8221;</a>.
@@ -1430,9 +1428,9 @@ bjam app1 lib1//lib1 gcc debug optimization=full
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="id3898010"></a>Building a Project</h4></div></div></div>
+<a name="id3997672"></a>Building a Project</h4></div></div></div>
<p>Often, a user builds a complete project, not just one main
- target. In fact, invoking <span class="command"><strong>bjam</strong></span> without
+ target. In fact, invoking <span class="command"><strong>b2</strong></span> without
arguments
builds the project defined in the current