as the first elements of result. Those usage requirements will be combined
with explicitly specified for the main target.
This is yet another step towards making 'main target classes' unnecessary.
* build/generators.jam
(try-one-generator): Check if generator returned usage requirements or not.
(construct): Make sure first element of result is always property set.
(many other methods): Induced changes
* tools/builtin.jam
(exe-target-class, lib-target-class): Remove.
(linking-generator, seached-lib-generator): Compute usage requirements.
(archiving-generator): New class
[SVN r26192]
write
using gcc : ... : ... : <cxxflags>foo <linkflags>bar ;
* tools/common.jam (handle-options): The login for setting the common
options.
[SVN r25767]
rules which create corresponding EXE/LIB targets.
The drawback with the previous approach, where there was a separate generator
for RSP file, was that the list of consumable target types is different,
depending on main target which uses RSP, and it's hard to express this
information.
* tools/builtin.jam
(response-file): Move to...
* tools/common.jam: Here.
* tools/msvc.jam
* tools/borland.jam
Split 'link' rule into 'link' and 'link.dll'. Call 'response-file'
from rules.
* tools/stage.jam
Fix a bug which cause RSP file to be staged incorrectly.
[SVN r20650]
it included MSVC...
* new/toolset.jam:
Allow action names with dots, so that we can set flags for
gcc.compile.c, gcc.compile and gcc and combine those flags.
* tools/gcc.jam: Use 'gcc' for compiling C files. There's still a problem:
'init' rules does not allow to configure name of C compiler. Also, don't
declare flags individually for gcc.link and gcc.link-dll.
* tools/borland.jam: Force C++ compile when needed.
[SVN r18774]
