From: Alexey Syomichev (asyomichev_at_[hidden])
Date: 2005-05-02 15:07:02
--- In jamboost_at_[hidden], David Abrahams <dave_at_b...> wrote:
> In v2, MSVC compilations use response files for everything,
> command-line options... and the response files are deleted, even
> compilation fails.
Funny thing is, .rsp stays there if compilation is successful, and
gets deleted automatically by bjam if compilation fails - the opposite
of the desired behavior.
> That makes it impossible to easily preprocess
> anything. I have a feeling that this arrangement will make many
> build tasks needlessly difficult. Solutions?
Today I tried to build on Windows a project that is normally built on
different UNIX flavors. This .rsp file issue is very annoying - it's
nearly impossible to debug build issues not being able to see the
command line. As a workaround, I added
copy "$(<:W)" "$(<:W).saved"
in msvc.actions.link and msvc.actions.compile. At least I can see the
rest of the command line in .rsp.saved, and even can re-run failed
actions after manually renaming .rsp.saved to .rsp
I guess the solution would be to exclude .rsp file from source target
list before any of msvc.actions.* called
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