- Move "file-touch-command" to "common.jam". It already has
"file-creation-command" so this one will be a good
companion.
Patch from Alexey Pakhunov.
[SVN r32061]
Removed special substitution behavior for $name as an
overgeneralization
Added prepend-path-variable command as a replacement
Fixed variables to conform to naming convention for module globals
[SVN r27094]
* util/print.jam: Do not quote the argument to the
'echo' command on windows. It's special, and does not need quotes.
Adding them will cause the quotes to always appear in the output,
which would be different behaviour from Unix.
* tools/common.jam (response-file): Add quotes here.
[SVN r26836]
enviroment variables in the list of values. No it's possible to add
an element to a variable.
* build/project.jam: Remove obsolete test.
* build/toolset.jam (find-property-subset): No longer local,
so that test can call it.
* test/test.jam: Import 'print' and 'common'.
* util/print.jam: Comment out failing unit test.
[SVN r26413]
Description: If the number of characters exceeds 2047, the cl command fails.
Plattform: MSYS shell, VC++ 7.1
Resolution: Using of the response file facility
* tools/msvc.jam
Change *compile* generators to produce RSP target too.
Change compile actions to use RSP file
And compile rules to call common.response-file
* tools/common.jam
(response-file): Write defines and includes.
Thanks to Johannes Brunen for the patch.
[SVN r26275]
write
using gcc : ... : ... : <cxxflags>foo <linkflags>bar ;
* tools/common.jam (handle-options): The login for setting the common
options.
[SVN r25767]
(check-tool): Try finding both first and the last element. This avoid
warning both in the case of "distcc g++", and in case of
'"set FOO=bar &&" como'.
(get-invocation-command): Returns the user-specified command even if
it can't be found anywere. This means user specified command will show
up in the command line, and even if it fails, it's less confusing than
command line with no compiler name at all.
[SVN r25765]
* tools/common.jam (check-init-parameters): New rule.
* tools/gcc.jam (init): Make use of the above.
* kernel/errors.jam (user-error): New rule.
[SVN r23084]
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]
