Re: [boost] [Review] FormalReview ofProposed Boost.ChronoLibrary Starts TOMORROW

Subject: Re: [boost] [Review] FormalReview ofProposed Boost.ChronoLibrary Starts TOMORROW
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2010-11-11 13:11:43

----- Original Message ----- 
From: "Paul A. Bristow" <pbristow_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Thursday, November 11, 2010 7:00 PM
Subject: Re: [boost] [Review] FormalReview ofProposed Boost.ChronoLibrary Starts TOMORROW

> 
>> -----Original Message-----
>> From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]]
>> On Behalf Of vicente.botet
>> Sent: Thursday, November 11, 2010 5:25 PM
>> To: boost_at_[hidden]
>> Subject: Re: [boost] [Review] Formal Review ofProposed Boost.ChronoLibrary
>> Starts TOMORROW
>> 
>> > I have now...
>> >
>> > #define BOOST_SYSTEM_INLINED
>> > #define BOOST_CHRONO_INLINED
>> >
>> > #include <boost/chrono/process_times.hpp>
>> > #include <cmath>
>> >
>> > produces the same output :-(
>> >
>> > I am including boost/trunk and boost/sandbox/chrono
>> >
>> > /Zi /nologo /W3 /WX- /Od /Oy- /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D
>> > "_UNICODE" /D "UNICODE" /GF- /Gm /EHsc /RTC1 /GS /fp:precise /Za
>> /Zc:wchar_t
>> > /Zc:forScope /Fp"Debug\chrono_runtime.pch" /Fa"Debug\" /Fo"Debug\"
>> > /Fd"Debug\vc100.pdb" /Gd /analyze- /errorReport:queue
>> >
>> > Perhaps I need to build the library?  Hopefully it won't hurt too much
> ;-)
>> 
>> Have you replaced the Boost.System directory?
> 
> I've just updated the boost/sandbox/chrono/ directory.
> 
> It has a system folder
> 
> Do I have to do something else?

Not that I know.
 
> (I assumed - the mother of all foul-ups - that putting sandbox first in
> include order would find any new version).

This seems a good assumption. I have not tested with this schema recently, I use to test on a single boost tree.

Sorry, but I'm out of ideas for the moment.

Best,
Vicente