Subject: [Boost-commit] svn:boost r77712 - trunk/tools/build/v2/doc/src
From: steven_at_[hidden]
Date: 2012-04-02 08:16:28
Author: steven_watanabe
Date: 2012-04-02 08:16:27 EDT (Mon, 02 Apr 2012)
New Revision: 77712
URL: http://svn.boost.org/trac/boost/changeset/77712
Log:
Document the type module.
Text files modified:
trunk/tools/build/v2/doc/src/reference.xml | 1 +
trunk/tools/build/v2/doc/src/tasks.xml | 18 +++++++++---------
2 files changed, 10 insertions(+), 9 deletions(-)
Modified: trunk/tools/build/v2/doc/src/reference.xml
==============================================================================
--- trunk/tools/build/v2/doc/src/reference.xml (original)
+++ trunk/tools/build/v2/doc/src/reference.xml 2012-04-02 08:16:27 EDT (Mon, 02 Apr 2012)
@@ -1949,6 +1949,7 @@
</section>
<xi:include href="path.xml"/>
+ <xi:include href="type.xml"/>
</section>
Modified: trunk/tools/build/v2/doc/src/tasks.xml
==============================================================================
--- trunk/tools/build/v2/doc/src/tasks.xml (original)
+++ trunk/tools/build/v2/doc/src/tasks.xml 2012-04-02 08:16:27 EDT (Mon, 02 Apr 2012)
@@ -495,12 +495,12 @@
<title>Custom commands</title>
<para>
- When you use most of main target rules, Boost.Build automatically figures
- what commands to run and it what order. As soon as you want to use new
+ For most main target rules, Boost.Build automatically figures out
+ the commands to run. When you want to use new
file types or support new tools, one approach is to extend Boost.Build to
- smoothly support them, as documented in <xref linkend="bbv2.extender"/>.
- However, if there is only a single place where the new tool is used, it
- might be easier to just explicitly specify the commands to run.
+ support them smoothly, as documented in <xref linkend="bbv2.extender"/>.
+ However, if the new tool is only used in a single place, it
+ might be easier just to specify the commands to run explicitly.
</para>
<para>
@@ -511,8 +511,8 @@
of source file, by running a command you specify. The <functionname>
notfile</functionname> rule allows you to run an arbitrary command,
without creating any files. And finaly, the <functionname>generate
- </functionname> rule allows you to describe transformation using
- Boost.Build's virtual targets. This is higher-level than file names that
+ </functionname> rule allows you to describe a transformation using
+ Boost.Build's virtual targets. This is higher-level than the file names that
the <functionname>make</functionname> 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.
@@ -532,8 +532,8 @@
them to become accessible. -->
<para>
- Suppose you want to create file <filename>file.out</filename> from file
- <filename>file.in</filename> by running command <command>
+ Suppose you want to create the file <filename>file.out</filename> from
+ the file <filename>file.in</filename> by running the command <command>
in2out</command>. Here is how you would do this in Boost.Build:
<programlisting>
make file.out : file.in : @in2out ;