Re: [boost] [1.40.0] Beta 1 release candidate available

Subject: Re: [boost] [1.40.0] Beta 1 release candidate available
From: Francesco Guerrieri (f.guerrieri_at_[hidden])
Date: 2009-08-17 12:03:29

On Wed, Aug 12, 2009 at 5:23 PM, Vladimir Prus<vladimir_at_[hidden]> wrote:
> Francesco Guerrieri wrote:
>> 1) in the Generating library status page
>> (boost-windows-2009-08-11\tools\regression\doc\library_status.html),
>> the path to library_test.bat is
>> ..\..\..\tools\regression\src\library_test and not
>> ..\..\..\tools\regression\library_test.
>> 2) another small glitch is that the Jamroot.jam didn't build the
>> library_status.exe. I added a #~ just before "explicit
>> library_status;" and it built, but contrarily to status.html
>> indications both process_jam_log.exe and library_status.exe were to be
>> found in a subdir of the bin\ folder (in my case they were to be found
>> under
>> boost-windows-2009-08-11\tools\regression\build\bin\msvc-10.0\release\threading-multi
>> )
>
> Hmm, why do you actually need that? What docs are you reading? I think the
> procedure involving run.py does not use those tools at all.

Hi, it appears to me that run.py does use those tools
(process_jam_log.exe and library_status.exe).
I had to copy them to a location where they could be found (.\ worked fine).
I continued to have some problem.
To double check if there's something not working with my machine (beta
of vs2010, beta of windows 7), today I did a run.py from scratch. It
worked fine, downloading from svn the sources (trunk branch),
compiling, running the tests (by the way, I got quite a few assertion
and core dumps with the tests, but they should appear in the uploaded
logs) and uploading them to the ftp server.

Maybe it's a solved problem by now, I have not yet read all the emails
:-) I just wanted to follow up.

Francesco