Subject: Re: [boost] [chrono] Thread clock compatibility problems on Android
From: Libor Bus (libor.bus_at_[hidden])
Date: 2011-05-13 13:05:11
thanks for the fast answer and your great library!
You can rely on #if defined ANDROID.
Regarding process_cpu_clock, I have experienced that following code provided
on Linux wrong text output, while on Windows was ok:
... some work
I was not even able to convert units:
stopwatch<process_cpu_clock>::duration d = t.stop();
real_time = microseconds( d.count().real).count(); // needs to be
multiplied by 1000
I'm not sure if I'm using conversion right way, but at least the stopclock
text output indicates some problem.
-- View this message in context: http://boost.2283326.n4.nabble.com/chrono-Thread-clock-compatibility-problems-on-Android-tp3520310p3520703.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk