diff options
Diffstat (limited to 'doc/html/bbv2/tasks.html')
| -rw-r--r-- | doc/html/bbv2/tasks.html | 36 |
1 files changed, 18 insertions, 18 deletions
diff --git a/doc/html/bbv2/tasks.html b/doc/html/bbv2/tasks.html index 06c80d1cc8..9c0ee36315 100644 --- a/doc/html/bbv2/tasks.html +++ b/doc/html/bbv2/tasks.html @@ -6,7 +6,7 @@ <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="up" href="../bbv2.html" title="Chapter 48. Boost.Build User Manual"> <link rel="prev" href="overview.html" title="Overview"> <link rel="next" href="reference.html" title="Reference"> </head> @@ -45,7 +45,7 @@ <div class="section"> <div class="titlepage"><div><div><h3 class="title"> <a name="bbv2.tasks.programs"></a>Programs</h3></div></div></div> -<a class="indexterm" name="idm45927672822368"></a><p> +<a class="indexterm" name="idp723522000"></a><p> Programs are created using the <code class="computeroutput">exe</code> rule, which follows the <a class="link" href="overview.html#bbv2.main-target-rule-syntax">common syntax</a>. For example: @@ -81,7 +81,7 @@ exe hello : hello.cpp some_library.lib /some_project//library <div class="section"> <div class="titlepage"><div><div><h3 class="title"> <a name="bbv2.tasks.libraries"></a>Libraries</h3></div></div></div> -<a class="indexterm" name="idm45927672813776"></a><p> +<a class="indexterm" name="idp723530528"></a><p> Library targets are created using the <code class="computeroutput">lib</code> rule, which follows the <a class="link" href="overview.html#bbv2.main-target-rule-syntax">common syntax </a>. For example: @@ -308,7 +308,7 @@ exe main : main.cpp static_libraries ; files. </p> <h4> -<a name="idm45927672755168"></a>Basic install</h4> +<a name="idp723589328"></a>Basic install</h4> <p> For installing a built target you should use the <code class="computeroutput">install</code> rule, which follows the <a class="link" href="overview.html#bbv2.main-target-rule-syntax"> @@ -347,7 +347,7 @@ install dist2 : hello helpers : <location>$(DIST) ; variables</a> </p> <h4> -<a name="idm45927672742400"></a>Installing with all dependencies</h4> +<a name="idp723602096"></a>Installing with all dependencies</h4> <p> Specifying the names of all libraries to install can be boring. The <code class="computeroutput">install</code> allows you to specify only the top-level executable @@ -371,8 +371,8 @@ install dist : hello otherwise, all found target will be installed. </p> <h4> -<a name="idm45927672737072"></a>Preserving Directory Hierarchy</h4> -<a class="indexterm" name="idm45927672736688"></a><p> +<a name="idp723607488"></a>Preserving Directory Hierarchy</h4> +<a class="indexterm" name="idp723607872"></a><p> By default, the <code class="computeroutput">install</code> rule will strip paths from its sources. So, if sources include <code class="filename">a/b/c.hpp</code>, the <code class="filename">a/b</code> part will be ignored. To make the @@ -396,7 +396,7 @@ install headers an entire directory tree. </p> <h4> -<a name="idm45927672728304"></a>Installing into Several Directories</h4> +<a name="idp723616192"></a>Installing into Several Directories</h4> <p> The <a class="link" href="tasks.html#bbv2.tasks.alias" title="Alias"><code class="computeroutput">alias</code></a> rule can be used when targets need to be installed into several directories: @@ -410,7 +410,7 @@ install install-lib : helper : /usr/lib ; </p> <p> Because the <code class="computeroutput">install</code> rule just copies targets, most free - features <a href="#ftn.idm45927672724368" class="footnote" name="idm45927672724368"><sup class="footnote">[13]</sup></a> have no + features <a href="#ftn.idp723620128" class="footnote" name="idp723620128"><sup class="footnote">[13]</sup></a> have no effect when used in requirements of the <code class="computeroutput">install</code> rule. The only two that matter are <a class="link" href="reference.html#bbv2.builtin.features.dependency"> <code class="varname">dependency</code></a> and, on Unix, <a class="link" href="reference.html#bbv2.reference.features.dll-path"><code class="varname">dll-path</code> @@ -499,7 +499,7 @@ rule run ( sources + : args * : input-files * : requirements * : target-name ? target-name</code></em>.output</code>. </p> <p> - <a class="indexterm" name="idm45927672693232"></a> + <a class="indexterm" name="idp723651392"></a> If the <code class="literal">preserve-test-targets</code> feature has the value <code class="literal">off</code>, then <code class="computeroutput">run</code> and the <code class="computeroutput">run-fail</code> rules will remove the executable after running it. This somewhat decreases @@ -553,7 +553,7 @@ unit-test helpers_test <p> By default, the executable is run directly. Sometimes, it is desirable to run the executable using some helper command. You - should use the this property to specify the name of the helper + should use this property to specify the name of the helper command. For example, if you write: </p> <pre class="programlisting"> @@ -600,7 +600,7 @@ unit-test helpers_test Boost.Build's virtual targets. This is higher-level than the file names that the <code class="computeroutput">make</code> rule operates with and allows you to create more than one target, create differently named targets depending on - properties or use more than one tool. + properties, or use more than one tool. </p> <p> The <code class="computeroutput">make</code> rule is used when you want to create @@ -761,7 +761,7 @@ exe main : main.cpp pch ; "parser.y". The latter source is converted into "parser.c" and "parser.h". Then, if "app.cpp" includes "parser.h", Boost.Build will detect this dependency. Moreover, since "parser.h" will be generated into a build - directory, the path to that directory will automatically added to include + directory, the path to that directory will automatically be added to the include path. </p> <p> @@ -783,7 +783,7 @@ exe app : app.cpp : <implicit-dependency>parser ; <div class="section"> <div class="titlepage"><div><div><h3 class="title"> <a name="bbv2.tasks.crosscompile"></a>Cross-compilation</h3></div></div></div> -<a class="indexterm" name="idm45927672611008"></a><p>Boost.Build supports cross compilation with the gcc and msvc +<a class="indexterm" name="idp723733632"></a><p>Boost.Build supports cross compilation with the gcc and msvc toolsets.</p> <p> When using gcc, you first need to specify your cross compiler @@ -794,13 +794,13 @@ using gcc : arm : arm-none-linux-gnueabi-g++ ; </pre> <p> After that, if the host and target os are the same, for example Linux, you can - just request that this compiler version to be used: + just request that this compiler version be used: </p> <pre class="screen"> b2 toolset=gcc-arm </pre> <p> - If you want to target different operating system from the host, you need + If you want to target a different operating system from the host, you need to additionally specify the value for the <code class="computeroutput">target-os</code> feature, for example: </p> @@ -815,14 +815,14 @@ b2 toolset=gcc-mingw <span class="bold"><strong>target-os=windows</strong></span <a class="link" href="reference.html#bbv2.reference.features.target-os">target-os feature</a>. </p> <p> - When using the msvc compiler, it's only possible to cross-compiler to a 64-bit system + When using the msvc compiler, it's only possible to cross-compile to a 64-bit system on a 32-bit host. Please see <a class="xref" href="reference.html#v2.reference.tools.compiler.msvc.64" title="64-bit support">the section called “64-bit support”</a> for details. </p> </div> <div class="footnotes"> <br><hr style="width:100; text-align:left;margin-left: 0"> -<div id="ftn.idm45927672724368" class="footnote"><p><a href="#idm45927672724368" class="para"><sup class="para">[13] </sup></a>see the definition of "free" in <a class="xref" href="reference.html#bbv2.reference.features.attributes" title="Feature Attributes">the section called “Feature Attributes”</a>.</p></div> +<div id="ftn.idp723620128" class="footnote"><p><a href="#idp723620128" class="para"><sup class="para">[13] </sup></a>see the definition of "free" in <a class="xref" href="reference.html#bbv2.reference.features.attributes" title="Feature Attributes">the section called “Feature Attributes”</a>.</p></div> </div> </div> <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr> |