boost/build
2
0
Fork 0
mirror of https://github.com/boostorg/build.git synced 2026-02-19 14:22:10 +00:00
Code Issues Projects Releases Wiki Activity

Cleaned up how Boost Build's generator selection implementation updates its cached information when a new target type is defined.

Browse Source 
[SVN r48649]
This commit is contained in:
Jurko Gospodnetić
2008-09-07 08:41:10 +00:00
parent b4c3eaeea8
commit fb5a27be5d
2 changed files with 7 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
v2/build/generators.jam
View File

@@ -60,12 +60,13 @@ if "--debug-generators" in [ modules.peek : ARGV ]
# Updated cached viable source target type information as needed after a new
# derived target type gets added. This is needed because if a target type is a
# viable source target type for some generator then all of the target type's
# derived target types are automatically viable as source target types for the
# same generator. Does nothing if a non-derived target type is passed to it.
# target type gets defined. This is needed because if a target type is a viable
# source target type for some generator then all of the target type's derived
# target types should automatically be considered as viable source target types
# for the same generator as well. Does nothing if a non-derived target type is
# passed to it.
#
rule update-viable-source-target-type-cache-with-derived-type ( type )
rule update-cached-information-with-a-new-type ( type )
{
local base-type = [ type.base $(type) ] ;
if $(base-type)

6
v2/build/type.jam
View File

@@ -80,11 +80,7 @@ rule register ( type : suffixes * : base-type ? )
# Adding a new derived type affects generator selection so we need to
# make the generator selection module update any of its cached
# information related to a new derived type being defined.
if $(base-type)
{
generators.update-viable-source-target-type-cache-with-derived-type
$(type) ;
}
generators.update-cached-information-with-a-new-type $(type) ;
}
}