The doxygen module is not really standalone, it requires Boost.Book XSL
stylesheets, and so needs to get their location from the boostbook module.
Previously, the doxygen.init module would get the stylesheet dir, and if
it's empty, would not declare some generators. So, if doxygen is initialized
before bookstbook, some conversion won't work.
Now, generators are defined in all cases, but when the action is run, we
check that boostbook was initialized.
[SVN r28313]
The doxygen module is not really standalone, it requires Boost.Book XSL
stylesheets, and so needs to get their location from the boostbook module.
Previously, the doxygen.init module would get the stylesheet dir, and if
it's empty, would not declare some generators. So, if doxygen is initialized
before bookstbook, some conversion won't work.
Now, generators are defined in all cases, but when the action is run, we
check that boostbook was initialized.
[SVN r28313]
Since standalone projects can be defined by toolset modules, invoked
from site-config.jam and user-config.jam, inheriting from not yet fully read
modules is tricky. Especially when toolset module is invoked from site-config.
We can't inherit from user-config, if we did not even start to load it!
[SVN r28212]
Since standalone projects can be defined by toolset modules, invoked
from site-config.jam and user-config.jam, inheriting from not yet fully read
modules is tricky. Especially when toolset module is invoked from site-config.
We can't inherit from user-config, if we did not even start to load it!
[SVN r28212]
The <tag> rule if often used in Jamfile like this: <tag>@$(__name__).rule.
The __name__ looks like Jamfile<jamfiles'directory>. When directory has
a dot, we we confused and took the part till the first dot as the
name of module.
Now, such values are processed closer to the definition point, where
we know the name of the module and don't need to guess it by looking at
the name.
Thanks to Juergen Hunold for the bug report.
[SVN r28063]
The <tag> rule if often used in Jamfile like this: <tag>@$(__name__).rule.
The __name__ looks like Jamfile<jamfiles'directory>. When directory has
a dot, we we confused and took the part till the first dot as the
name of module.
Now, such values are processed closer to the definition point, where
we know the name of the module and don't need to guess it by looking at
the name.
Thanks to Juergen Hunold for the bug report.
[SVN r28063]
* Add "nothing" fake target.
testing.jam:
* Prevent build-no non-targets from attempting to dump the test info.
* Add dumping of an association from test ID to test target name. So that we can direct automated testing to build specific targets base on the IDs.
[SVN r27939]
