diff options
Diffstat (limited to 'doc/html/bbv2/tutorial.html')
-rw-r--r-- | doc/html/bbv2/tutorial.html | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/doc/html/bbv2/tutorial.html b/doc/html/bbv2/tutorial.html index c96f99e872..d167c10204 100644 --- a/doc/html/bbv2/tutorial.html +++ b/doc/html/bbv2/tutorial.html @@ -6,8 +6,8 @@ <link rel="stylesheet" href="../../../doc/src/boostbook.css" type="text/css"> <meta name="generator" content="DocBook XSL Stylesheets V1.79.1"> <link rel="home" href="../index.html" title="The Boost C++ Libraries BoostBook Documentation Subset"> -<link rel="up" href="../bbv2.html" title="Chapter 45. Boost.Build User Manual"> -<link rel="prev" href="../bbv2.html" title="Chapter 45. Boost.Build User Manual"> +<link rel="up" href="../bbv2.html" title="Chapter 49. Boost.Build User Manual"> +<link rel="prev" href="../bbv2.html" title="Chapter 49. Boost.Build User Manual"> <link rel="next" href="overview.html" title="Overview"> </head> <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> @@ -31,7 +31,7 @@ <dt><span class="section"><a href="tutorial.html#bbv2.tutorial.properties">Properties</a></span></dt> <dt><span class="section"><a href="tutorial.html#bbv2.tutorial.hierarchy">Project Hierarchies</a></span></dt> <dt><span class="section"><a href="tutorial.html#bbv2.tutorial.libs">Dependent Targets</a></span></dt> -<dt><span class="section"><a href="tutorial.html#bbv2.tutorial.linkage">Static and shared libaries</a></span></dt> +<dt><span class="section"><a href="tutorial.html#bbv2.tutorial.linkage">Static and shared libraries</a></span></dt> <dt><span class="section"><a href="tutorial.html#bbv2.tutorial.conditions">Conditions and alternatives</a></span></dt> <dt><span class="section"><a href="tutorial.html#bbv2.tutorial.prebuilt">Prebuilt targets</a></span></dt> </dl></div> @@ -204,8 +204,8 @@ exe hello requirements, the target requirements usually override (or, in the case of “free”” features like <code class="varname"><include></code>, - <a href="#ftn.idm45927673411792" class="footnote" name="idm45927673411792"><sup class="footnote">[11]</sup></a> - augments) the build request. + <a href="#ftn.idp636209664" class="footnote" name="idp636209664"><sup class="footnote">[32]</sup></a> + augment) the build request. </p> <div class="tip"><table border="0" summary="Tip"> <tr> @@ -316,7 +316,7 @@ top/ in its requirements, then all of its subprojects will have it in their requirements, too. Of course, any project can add - include paths to those specified by its parents. <a href="#ftn.idm45927673383648" class="footnote" name="idm45927673383648"><sup class="footnote">[12]</sup></a> + include paths to those specified by its parents. <a href="#ftn.idp636237872" class="footnote" name="idp636237872"><sup class="footnote">[33]</sup></a> More details can be found in <a class="xref" href="overview.html#bbv2.overview.projects" title="Projects">the section called “Projects”</a>. </p> @@ -423,7 +423,7 @@ lib foo <span class="special">:</span> foo.cpp <span class="special">;</span></p <p> Usage requirements are applied not to the target being declared but to its - dependants. In this case, <code class="literal"><include>.</code> will be + dependents. In this case, <code class="literal"><include>.</code> will be applied to all targets that directly depend on <code class="filename">foo</code>. </p> <p> @@ -459,7 +459,7 @@ exe app : app.cpp /library-example/foo//bar ;</pre> </tr> <tr><td align="left" valign="top"> <p>If you want all applications in some project to link to a certain - library, you can avoid having to specify it directly the sources of + library, you can avoid having to specify directly the sources of every target by using the <code class="varname"><library></code> property. For example, if <code class="filename">/boost/filesystem//fs</code> should be linked to all applications in your project, you can add @@ -475,7 +475,7 @@ project </div> <div class="section"> <div class="titlepage"><div><div><h3 class="title"> -<a name="bbv2.tutorial.linkage"></a>Static and shared libaries</h3></div></div></div> +<a name="bbv2.tutorial.linkage"></a>Static and shared libraries</h3></div></div></div> <p> Libraries can be either <span class="emphasis"><em>static</em></span>, which means they are included in executable files that use them, or <span class="emphasis"><em>shared</em></span> @@ -670,8 +670,8 @@ exe app <span class="special">:</span> app.cpp ../util/lib2//lib2 <span class="s <p> As with any target, the alternative selected depends on the properties - propagated from <code class="filename">lib2</code>'s dependants. If we build the - release and debug versions of <code class="filename">app</code> will be linked + propagated from <code class="filename">lib2</code>'s dependents. If we build the + release and debug versions of <code class="filename">app</code> it will be linked with <code class="filename">lib2_release.a</code> and <code class="filename">lib2_debug.a </code>, respectively. </p> @@ -713,10 +713,10 @@ lib pythonlib <span class="special">:</span> <span class="special">:</span> < </div> <div class="footnotes"> <br><hr style="width:100; text-align:left;margin-left: 0"> -<div id="ftn.idm45927673411792" class="footnote"><p><a href="#idm45927673411792" class="para"><sup class="para">[11] </sup></a> +<div id="ftn.idp636209664" class="footnote"><p><a href="#idp636209664" class="para"><sup class="para">[32] </sup></a> See <a class="xref" href="reference.html#bbv2.reference.features.attributes" title="Feature Attributes">the section called “Feature Attributes”</a> </p></div> -<div id="ftn.idm45927673383648" class="footnote"><p><a href="#idm45927673383648" class="para"><sup class="para">[12] </sup></a>Many +<div id="ftn.idp636237872" class="footnote"><p><a href="#idp636237872" class="para"><sup class="para">[33] </sup></a>Many features will be overridden, rather than added-to, in subprojects. See <a class="xref" href="reference.html#bbv2.reference.features.attributes" title="Feature Attributes">the section called “Feature Attributes”</a> for more information</p></div> |