From: Zbynek Winkler (zw-bjam_at_[hidden])
Date: 2005-10-30 09:39:10
Reece Dunn wrote:
>The results of the discussion on the "[BBv2] fix for response file
>regeneration" thread was to have builtin support for response files
>using the @(...) syntax based on Matt Armstrong's perforce Jam branch.
>The bjam-response.diff patch adds @(...) syntax support for NT builds of
>BJam. This is based on Matt's code but was written from scratch and is
>improved from my initial submission. When you use @(...) the code (in
>variable.c) expands the variables in the '...' to a temporary file and
>then outputs the location of that file.
>The response.diff patch is the BBv2 changes needed for native response
>file support. This removes the response file logic from common.jam and
>modifies msvc.jam and cw.jam to use the new syntax.
The new builtin is enabled only for NT? IMHO it is generally useful to
be able to output the contents of a variable to a file. It does not need
to be only a response file for msvc or cw...
-- http://zw.matfyz.cz/ http://robotika.cz/ Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk