|
Boost-Commit : |
Subject: [Boost-commit] svn:boost r48591 - trunk/tools/build/v2/build
From: jurko.gospodnetic_at_[hidden]
Date: 2008-09-04 20:39:59
Author: jurko
Date: 2008-09-04 20:39:58 EDT (Thu, 04 Sep 2008)
New Revision: 48591
URL: http://svn.boost.org/trac/boost/changeset/48591
Log:
Added a comment to Boost Build's build/generators.jam module pointing to a mailing list thread containing an idea for refactoring Boost Build's Jamfile parsing so nothing would invalidate Boost Build's cached generator selection related viable source type information instead of having to work around the issues by clearing the cache when needed.
Text files modified:
trunk/tools/build/v2/build/generators.jam | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
Modified: trunk/tools/build/v2/build/generators.jam
==============================================================================
--- trunk/tools/build/v2/build/generators.jam (original)
+++ trunk/tools/build/v2/build/generators.jam 2008-09-04 20:39:58 EDT (Thu, 04 Sep 2008)
@@ -693,6 +693,12 @@
# type information would be to expand it with additional source types or
# even better - mark it as needing to be expanded on next use.
#
+ # Also see the http://thread.gmane.org/gmane.comp.lib.boost.build/19077
+ # mailing list thread for an even more advanced idea of how we could convert
+ # Boost Build's Jamfile processing, target selection and generator selection
+ # into separate steps which would prevent these caches from ever being
+ # invalidated.
+ #
# For now we just clear all the cached viable source target type information
# that does not simply state 'all types' and may implement a more detailed
# algorithm later on if it becomes needed.
Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk