path: root/doc/html/bbv2/extender.html
diff options
Diffstat (limited to 'doc/html/bbv2/extender.html')
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/html/bbv2/extender.html b/doc/html/bbv2/extender.html
index ee7ec86724..23b7d38a0e 100644
--- a/doc/html/bbv2/extender.html
+++ b/doc/html/bbv2/extender.html
@@ -95,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.idp639100864" class="footnote" name="idp639100864"><sup class="footnote">[19]</sup></a>
+ <a href="#ftn.idp620044384" class="footnote" name="idp620044384"><sup class="footnote">[35]</sup></a>
<p>The <a class="link" href="reference.html#bbv2.reference.class.abstract-target.generate">generate</a>
method takes the build properties
@@ -187,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.idp639141024" class="footnote" name="idp639141024"><sup class="footnote">[20]</sup></a>
+ ones, as necessary.<a href="#ftn.idp620084560" class="footnote" name="idp620084560"><sup class="footnote">[36]</sup></a>
Here are a couple of examples:
<pre class="programlisting">
@@ -209,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="idp639147296"></a>
+ <a class="indexterm" name="idp620090768"></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
@@ -494,7 +494,7 @@ generators.register-composing mex.mex : CPP LIB : MEX ;
<p>(Need a note about UNIX)</p>
-<a name="idp639220784"></a>Custom generator classes</h4>
+<a name="idp620164352"></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,
@@ -702,7 +702,7 @@ actions inline-file
-<a name="idp639253120"></a>Steps for adding a feauture</h4>
+<a name="idp620196032"></a>Steps for adding a feauture</h4>
<p>Adding a feature requires three steps:
@@ -743,7 +743,7 @@ actions inline-file
-<a name="idp639264144"></a>Another example</h4>
+<a name="idp620207056"></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
@@ -824,7 +824,7 @@ rule link
-<a name="idp639276592"></a>Variants and composite features.</h4>
+<a name="idp620219504"></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.
@@ -1022,9 +1022,9 @@ using yfc ;
<div class="footnotes">
<br><hr style="width:100; text-align:left;margin-left: 0">
-<div id="ftn.idp639100864" class="footnote"><p><a href="#idp639100864" class="para"><sup class="para">[19] </sup></a>This name is historic, and will be eventuall changed to
+<div id="ftn.idp620044384" class="footnote"><p><a href="#idp620044384" class="para"><sup class="para">[35] </sup></a>This name is historic, and will be eventuall changed to
<code class="computeroutput">metatarget</code></p></div>
-<div id="ftn.idp639141024" class="footnote"><p><a href="#idp639141024" class="para"><sup class="para">[20] </sup></a>This create-then-register pattern is caused by limitations
+<div id="ftn.idp620084560" class="footnote"><p><a href="#idp620084560" class="para"><sup class="para">[36] </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>