summaryrefslogtreecommitdiff
path: root/doc/html/bbv2/extender.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/bbv2/extender.html')
-rw-r--r--doc/html/bbv2/extender.html19
1 files changed, 10 insertions, 9 deletions
diff --git a/doc/html/bbv2/extender.html b/doc/html/bbv2/extender.html
index 8dde06db5b..8d36a81e7a 100644
--- a/doc/html/bbv2/extender.html
+++ b/doc/html/bbv2/extender.html
@@ -1,3 +1,4 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
@@ -94,7 +95,7 @@
and can be called with specific properties to generate concrete
targets. At the code level it is represented by an instance of
class derived from <a class="link" href="reference.html#bbv2.reference.class.abstract-target" title="Class abstract-target">abstract-target</a>.
- <a href="#ftn.idp546209248" class="footnote" name="idp546209248"><sup class="footnote">[16]</sup></a>
+ <a href="#ftn.idp552609392" class="footnote" name="idp552609392"><sup class="footnote">[16]</sup></a>
</p>
<p>The <a class="link" href="reference.html#bbv2.reference.class.abstract-target.generate">generate</a>
method takes the build properties
@@ -186,7 +187,7 @@ local t = [ new file-target $(name) : CPP : $(project) : $(a) ] ;
returning targets you should pass them via the <code class="computeroutput">virtual-target.register</code>
function, besides allowing Boost.Build to track which virtual targets
got created for each metatarget, this will also replace targets with previously created identical
- ones, as necessary.<a href="#ftn.idp546249408" class="footnote" name="idp546249408"><sup class="footnote">[17]</sup></a>
+ ones, as necessary.<a href="#ftn.idp552649488" class="footnote" name="idp552649488"><sup class="footnote">[17]</sup></a>
Here are a couple of examples:
</p>
<pre class="programlisting">
@@ -208,7 +209,7 @@ return [ sequence.transform virtual-target.register : $(targets) ] ;
<p>In practice, most files have specific types, and most tools
consume and produce files of specific type. To take advantage of this
fact, Boost.Build defines concept of target type and
- <a class="indexterm" name="idp546255616"></a>
+ <a class="indexterm" name="idp552655760"></a>
<em class="firstterm">generators</em>, and has special metatarget class
<a class="link" href="reference.html#bbv2.reference.class.typed-target" title="Class typed-target">typed-target</a>. Target type is merely an
identifier. It is associated with a set of file extensions that
@@ -493,7 +494,7 @@ generators.register-composing mex.mex : CPP LIB : MEX ;
</p>
<p>(Need a note about UNIX)</p>
<h4>
-<a name="idp546328640"></a>Custom generator classes</h4>
+<a name="idp552728784"></a>Custom generator classes</h4>
<p>The standard generators allows you to specify source and target
types, an action, and a set of flags. If you need anything more complex,
@@ -701,7 +702,7 @@ actions inline-file
<p>
</p>
<h4>
-<a name="idp546361232"></a>Steps for adding a feauture</h4>
+<a name="idp552760352"></a>Steps for adding a feauture</h4>
<p>Adding a feature requires three steps:
</p>
@@ -742,7 +743,7 @@ actions inline-file
<p>
</p>
<h4>
-<a name="idp546372256"></a>Another example</h4>
+<a name="idp552771376"></a>Another example</h4>
<p>Here's another example.
Let's see how we can make a feature that refers to a target. For example,
when linking dynamic libraries on Windows, one sometimes needs to
@@ -823,7 +824,7 @@ rule link
</li>
</ol></div>
<h4>
-<a name="idp546384704"></a>Variants and composite features.</h4>
+<a name="idp552783824"></a>Variants and composite features.</h4>
<p>Sometimes you want to create a shortcut for some set of
features. For example, <code class="computeroutput">release</code> is a value of
<code class="computeroutput">&lt;variant&gt;</code> and is a shortcut for a set of features.
@@ -1021,9 +1022,9 @@ using yfc ;
</div>
<div class="footnotes">
<br><hr style="width:100; text-align:left;margin-left: 0">
-<div id="ftn.idp546209248" class="footnote"><p><a href="#idp546209248" class="para"><sup class="para">[16] </sup></a>This name is historic, and will be eventuall changed to
+<div id="ftn.idp552609392" class="footnote"><p><a href="#idp552609392" class="para"><sup class="para">[16] </sup></a>This name is historic, and will be eventuall changed to
<code class="computeroutput">metatarget</code></p></div>
-<div id="ftn.idp546249408" class="footnote"><p><a href="#idp546249408" class="para"><sup class="para">[17] </sup></a>This create-then-register pattern is caused by limitations
+<div id="ftn.idp552649488" class="footnote"><p><a href="#idp552649488" class="para"><sup class="para">[17] </sup></a>This create-then-register pattern is caused by limitations
of the Boost.Jam language. Python port is likely to never create duplicate targets.</p></div>
</div>
</div>