[Boost-commit] svn:boost r78684 - trunk/tools/build/v2/test

Subject: [Boost-commit] svn:boost r78684 - trunk/tools/build/v2/test
From: jurko.gospodnetic_at_[hidden]
Date: 2012-05-27 11:10:24

Author: jurko
Date: 2012-05-27 11:10:24 EDT (Sun, 27 May 2012)
New Revision: 78684
URL: http://svn.boost.org/trac/boost/changeset/78684

Log:
Commented two new test case ideas for Boost Build's timedata test - 'time' targets with sources representing more than one virtual target and sources representing a virtual target that gets built by multiple actions in sequence.
Text files modified: 
   trunk/tools/build/v2/test/timedata.py |    14 ++++++++++++++                          
   1 files changed, 14 insertions(+), 0 deletions(-)

Modified: trunk/tools/build/v2/test/timedata.py
==============================================================================
--- trunk/tools/build/v2/test/timedata.py	(original)
+++ trunk/tools/build/v2/test/timedata.py	2012-05-27 11:10:24 EDT (Sun, 27 May 2012)
@@ -7,6 +7,20 @@
 
 # Tests the build step timing facilities.
 
+# TODO: Missing tests:
+# 1. 'time' target with a source target representing more than one virtual
+#    target. This happens in practice, e.g. when using the time rule on a msvc
+#    exe target whose generator actually constructs an EXE and a PDB target.
+#    When this is done - only te main virtual target's constructing action
+#    should be timed.
+# 2. 'time' target with a source target representing a virtual target that
+#    actually gets built by multiple actions run in sequence. In that case a
+#    separate timing result should be reported for each of those actions. This
+#    happens in practice, e.g. when using the time rule on a msvc exe target
+#    which first gets created as a result of some link action and then its
+#    manifest gets embedded inside it as a resource using a separate action
+#    (assuming an appropriate property has been set for this target - see the
+#    msvc module for details).
 
 import BoostBuild
 import re