I switched my AbsoluteTime variables over to uint64_t, but was still
running into problems.
Some calls I make to IOTimerEventSource instance and IOAudioEngine
instance in my code were still expecting
an AbsoluteTime value as an argument.
So I had to cast to AbsoluteTime in these cases, using an example
from qa1398:
Kind of confusing, I must say, but now it seems to work.
Tommy
On Jun 28, 2005, at 1:48 PM, Mark Cookson wrote:
I noticed this too. They appear to have switched from using "wide"
to "long
long" so you're no longer dealing with the wide structure, but
instead the
intrinsic type long long.
Basically you don't need the macros anymore, you can just add,
subtract, and
compare the times since they are native types.
I'm hoping that all of the code that was returning or using these
types is
converted as well, though I'm wondering what I'll do when I have to
make a
binary for 10.2.8 as well as Intel.
--
Mark Cookson
M-Audio, a part of Avid
225 Locust St.
Hudson, WI 54016
On 6/27/05 4:16 PM, "Tommy Schell" <email@hiddenrgent-
design.com> wrote:
Hi,
I have a timer set up in my driver, for Tiger and Xcode 2.0 I now get
compile errors regarding some of the kernel
timing conversion routines, which I didn't get before:
1) I was using ADD_ABSOLUTETIME (AbsoluteTime &t1, AbsoluteTime
&t2) , but now I'm told it is "not declared in this scope".
Is there a replacement for this or why do I get this error now?
2) Then I get several errors saying "cannot convert from
AbsoluteTime* to uint64_t* for:
get_clock_uptime(uint64_t*);
nanoseconds_to_absolutetime(uint64_t, uint64_t*);
