2
0
mirror of https://github.com/boostorg/build.git synced 2026-02-16 01:12:13 +00:00

Doc tweaks

[SVN r36438]
This commit is contained in:
Vladimir Prus
2006-12-16 23:04:45 +00:00
parent 8d78823ef9
commit 13a3741a20
3 changed files with 60 additions and 2 deletions

View File

@@ -668,7 +668,7 @@ exe a : a.cpp ; # a.cpp is the only source file
exe b : [ glob *.cpp ] ; # all .cpp files in this directory are sources
</programlisting>
Unless you specify a file with an absolute path, the name is
considered relative to the source directory&#x2014;which is typically
considered relative to the source directory&#x200A;&#x2014;&#x200A;which is typically
the directory where the Jamfile is located, but can be changed as
described in <xref linkend=
"bbv2.advanced.projects.attributes.projectrule"/>.

View File

@@ -385,7 +385,7 @@ generators.register [ new itrace-generator nm.itrace : EXE : ITRACE ] ;
program will import itself, not the extension. Here's how it can be
done:
<programlisting>
rule run ( project name ? : property-set : sources * : multiple ? )
rule run ( project name ? : property-set : sources * )
{
local python ;
for local s in $(sources)

58
v2/doc/src/fragments.xml Normal file
View File

@@ -0,0 +1,58 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter PUBLIC "-//Boost//DTD BoostBook XML V1.0//EN"
"http://www.boost.org/tools/boostbook/dtd/boostbook.dtd">
<chapter>
<section id="root_option">
<varlistentry>
<term><literal>root</literal></term>
<!-- At present, this option is only used to set LD_LIBRARY_PATH
when running tests, and matters only if compiler's lib directory
is not in LD_LIBRARY_PATH -->
<listitem><para>Specifies root directory of the compiler
installation. This option is necessary only if it's not possible
to detect this information from the compiler command&#x2014;for
example if the specified compiler command is a user script. </para>
</listitem>
</varlistentry>
</section>
<section id="common_options">
<varlistentry>
<term><literal>cflags</literal></term>
<listitem><para>Specifies additional compiler flags that
will be used when compiling C sources.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>cxxflags</literal></term>
<listitem><para>Specifies additional compiler flags that
will be used when compiling C++ sources.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>compileflags</literal></term>
<listitem><para>Specifies additional compiler flags that
will be used when compiling both C and C++ sources.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>linkflags</literal></term>
<listitem><para>Specifies additional command line options
that will be passed to the linker.</para>
</listitem>
</varlistentry>
</section>
</chapter>