From 93886c01433ee9bf2b494241d33acdda88959755 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jurko=20Gospodneti=C4=87?= Date: Fri, 5 Sep 2008 00:39:58 +0000 Subject: [PATCH] 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. [SVN r48591] --- v2/build/generators.jam | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/v2/build/generators.jam b/v2/build/generators.jam index a87dab34e..a86e1a2f2 100644 --- a/v2/build/generators.jam +++ b/v2/build/generators.jam @@ -693,6 +693,12 @@ rule register ( g ) # 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.