diff --git a/doc/architecture.html b/doc/architecture.html index a69f7fa28..98be6b4b4 100644 --- a/doc/architecture.html +++ b/doc/architecture.html @@ -21,12 +21,12 @@ br.clear { clear: left } div.alert { color: red } table { align: center; border: thin; } - + + - build request, build request expansion and directly requested targets + - conditional properties + -->

-

Support for different scanning algorithm

+

Support for different scanning algorithms

Different scanning algorithm are encapsulated by objects called "scanners". Please see the documentation for "scanner" module for more @@ -96,10 +96,10 @@

Ability to scan the same file several times

-

As said above, it's possible to compile C++ file twice, with different - include path. Therefore, include dependencies for those compilation can - be different. The problem is that bjam does not allow several scans of - the same target.

+

As said above, it's possible to compile a C++ file twice, with + different include paths. Therefore, include dependencies for those + compilations can be different. The problem is that bjam does not allow + several scans of the same target.

The solution in Boost.Build is straigtforward. When a virtual target is converted to bjam target (via virtual-target.actualize @@ -107,9 +107,10 @@ will create different bjam targets for different scanners.

All targets with specific scanner are made dependent on target without - scanner, which target is always created. This is done in case target is - updated. The updating action will specify target without scanner and - output, and we need targets with scanner to be updated as well.

+ scanner, which target is always created. This is done in case the target + is updated. The updating action will be associated with target without + scanner, but if sources for that action are touched, all targets — + with scanner and without should be considered outdated.

For example, assume that "a.cpp" is compiled by two compilers with different include path. It's also copied into some install location. In diff --git a/v2/doc/architecture.html b/v2/doc/architecture.html index a69f7fa28..98be6b4b4 100644 --- a/v2/doc/architecture.html +++ b/v2/doc/architecture.html @@ -21,12 +21,12 @@ br.clear { clear: left } div.alert { color: red } table { align: center; border: thin; } - + + - build request, build request expansion and directly requested targets + - conditional properties + -->

-

Support for different scanning algorithm

+

Support for different scanning algorithms

Different scanning algorithm are encapsulated by objects called "scanners". Please see the documentation for "scanner" module for more @@ -96,10 +96,10 @@

Ability to scan the same file several times

-

As said above, it's possible to compile C++ file twice, with different - include path. Therefore, include dependencies for those compilation can - be different. The problem is that bjam does not allow several scans of - the same target.

+

As said above, it's possible to compile a C++ file twice, with + different include paths. Therefore, include dependencies for those + compilations can be different. The problem is that bjam does not allow + several scans of the same target.

The solution in Boost.Build is straigtforward. When a virtual target is converted to bjam target (via virtual-target.actualize @@ -107,9 +107,10 @@ will create different bjam targets for different scanners.

All targets with specific scanner are made dependent on target without - scanner, which target is always created. This is done in case target is - updated. The updating action will specify target without scanner and - output, and we need targets with scanner to be updated as well.

+ scanner, which target is always created. This is done in case the target + is updated. The updating action will be associated with target without + scanner, but if sources for that action are touched, all targets — + with scanner and without should be considered outdated.

For example, assume that "a.cpp" is compiled by two compilers with different include path. It's also copied into some install location. In