Boost Testing :
From: Beman Dawes (bdawes_at_[hidden])
Date: 2008-06-28 08:46:47
Rene Rivera wrote:
> Richard Webb wrote:
>> Nicola Musatti <Nicola.Musatti <at> gmail.com> writes:
>>> Is there a way to look at the process_jam_log command line that
>>> causes the
>>> problem? I'll try and perform a regression run to see what is going
>>> unfortunately I won't be able to do it before sunday or monday.
>>> Nicola Musatti
>> The command line is:
>> "E:\test\results" 0<"E:\test\results\bjam.log"
>> I had a look at process_jam_log.cpp, and i think the problem might be
>> in the
>> target_directory() function:
>> The full pjl log contains things like:
>> line 3244: compile-c-c++
>> line_start: compile-c-c++
>> target_directory( "compile-c-c++
>> *****Warning - can't open output file:
>> One of the recent changes in pjl was to change line 158 from
>> else temp.erase( 0, locate_root.string().size()+1 );
>> else if ( temp == '/' ) temp.erase( 0,
>> locate_root.string().size()+1 );
>> I tried changing it back, and that seems to have fixed it.
> Many, many, thanks for finding that! I've gone ahead and reverted that
That line was part of a patch from Nicola Musatti. Nicola, what was that
change trying to accomplish?