Subject: [Boost-commit] svn:boost r79582 - trunk/tools/build/v2/build
From: jurko.gospodnetic_at_[hidden]
Date: 2012-07-18 09:26:03
Author: jurko
Date: 2012-07-18 09:26:02 EDT (Wed, 18 Jul 2012)
New Revision: 79582
URL: http://svn.boost.org/trac/boost/changeset/79582
Log:
Minor stylistic changes made to the Python Boost Build comment updated in the previous commit.
Text files modified:
trunk/tools/build/v2/build/virtual_target.py | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
Modified: trunk/tools/build/v2/build/virtual_target.py
==============================================================================
--- trunk/tools/build/v2/build/virtual_target.py (original)
+++ trunk/tools/build/v2/build/virtual_target.py 2012-07-18 09:26:02 EDT (Wed, 18 Jul 2012)
@@ -809,12 +809,12 @@
# when an actual Boost Jam action is encountered while we do this even
# if our Boost Build action is actually modeling a rule that will then
# register one or more Boost Jam actions. In that case our INCLUDES
- # relation added here will affect the build behaviour but it will not be
- # solving any actual problem. The only thing it might seem like it is
- # doing is forcing multiple separate actions to be run all together or
- # none at all but it will not do that completely either - it would miss
- # the case when one of the action targets depends on a target that needs
- # to be updated and another does not.
+ # relation added here will affect the build behaviour but it will no
+ # be solving any actual problem. The only thing it might seem like it
+ # is doing is forcing multiple separate actions to be run all together
+ # or none at all but it will not do that completely either - it would
+ # miss the case when one of the action targets depends on a target that
+ # needs to be updated and another does not.
if len(actual_targets) > 1:
bjam.call("INCLUDES", actual_targets, actual_targets)