boost/build
2
0
Fork 0
mirror of https://github.com/boostorg/build.git synced 2026-02-15 00:52:16 +00:00
Code Issues Projects Releases Wiki Activity

Add a comment as to why searched-lib instances with different properties

Browse Source 
won't be confused.


[SVN r17103]
This commit is contained in:
Vladimir Prus
2003-01-31 08:17:05 +00:00
parent 84a622bd27
commit 885264872c
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
src/tools/builtin.jam
View File

@@ -331,6 +331,16 @@ rule searched-lib-generator ( )
{
shared = true ;
}
# It might seem that, as we ignore all properties, searched-lib-targets
# with different properties can be confused. This is not true.
# searched-lib-target is pretty special. Although it's actualized into
# some real Jam target as all virtual targets, that Jam target is unused.
# Instead, the link-action class specially processes such targets, adding
# appropriate <find-*-library> properties. So, if one searched lib is build
# with two different properties, we'll get two different virtual targets.
# The library names will be correctly set, although both virtual targets will
# correspond to one Jam target.
return [ new searched-lib-target $(name) : $(project) : $(shared)
: [ feature.get-values <name> : $(properties) ]
: [ feature.get-values <search> : $(properties) ]