[Boost-commit] svn:boost r79996 - trunk/tools/build/v2/doc/src

Subject: [Boost-commit] svn:boost r79996 - trunk/tools/build/v2/doc/src
From: jurko.gospodnetic_at_[hidden]
Date: 2012-08-13 01:11:50

Author: jurko
Date: 2012-08-13 01:11:50 EDT (Mon, 13 Aug 2012)
New Revision: 79996
URL: http://svn.boost.org/trac/boost/changeset/79996

Log:
Updated Boost Build documentation to note that the virtual-target.register rule should be called for each created virtual-target instance and not only to remove duplicates when there is a chance of creating multiple matching virtual targets. Without this call, Boost Build fails to track which virtual targets get created for each metatarget.
Text files modified: 
   trunk/tools/build/v2/doc/src/extending.xml |     5 +++--                                   
   1 files changed, 3 insertions(+), 2 deletions(-)

Modified: trunk/tools/build/v2/doc/src/extending.xml
==============================================================================
--- trunk/tools/build/v2/doc/src/extending.xml	(original)
+++ trunk/tools/build/v2/doc/src/extending.xml	2012-08-13 01:11:50 EDT (Mon, 13 Aug 2012)
@@ -181,8 +181,9 @@
         once with the same properties. Returning to different instance of <classname>file-target</classname>
         that correspond to the same file clearly will result in problems. Therefore, whenever
         returning targets you should pass them via the <code>virtual-target.register</code>
-        function, that will replace targets with previously created identical ones, as
-        necessary.<footnote><para>This create-then-register pattern is caused by limitations 
+        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.<footnote><para>This create-then-register pattern is caused by limitations 
         of the Boost.Jam language. Python port is likely to never create duplicate targets.</para></footnote>
         Here are a couple of examples:
 <programlisting>