From: Jurko Gospodnetiæ (jurko_for_boost_at_[hidden])
Date: 2007-05-20 09:46:53
Hi Dean.
>> 1. Is there an easy way to see a response file used for a failed
>> build action? The best workaround we found so far is temporarily denying
>> ourselves the right to delete files from the target folder and so
>> preventing Boost.Build to remove the file. :-)))
>>
>
> I don't know about easy, but I imagine using pipes on Unix... I'm not
> sure I understand what you mean though by "see a response file used
> for a failed build action". If you mean the outputs of an error for
> building 'object.o' into a file named 'object_o_fail.log', then I
> guess it's a nice to have worth exploring. :-)
Nope, did not mean this.
When you build something using the msvc toolset all the parameters
passed to compilers/linkers get packaged into response files. When you
look at the shell commands bjam executes you just see the
compiler/linker call with the name of the response file passed as a
parameter. To see exactly which compiler/linker parameters were used you
need to open that response file but if a compiler/linker call fails then
its corresponding response file gets deleted together with any other
partially built targets. :-(
Best regards,
Jurko Gospodnetiæ