Re: [boost] [build] Tests automatically create header links, but library builds do not

Andrey Semashev wrote:

My opinion is that any tool that intends to parse C++ should do it right, Boost.Build included.

The tools do parse it right. It is not possible for a dependency scanner to figure out what macros are defined to what, in general - the predefined macros differ across compilers and systems, as do the explicit -D arguments. But even if the tool could figure it out somehow, it should not. That's because the configuration where the dependency scanner is being run may not match the configuration in which the dependency information will be used.