Re: Getting 10.4 OSAtomic.h when targeting 10.5
Re: Getting 10.4 OSAtomic.h when targeting 10.5
- Subject: Re: Getting 10.4 OSAtomic.h when targeting 10.5
- From: Chris Espinosa <email@hidden>
- Date: Sat, 16 May 2009 14:02:25 -0700
On May 16, 2009, at 1:39 PM, Wade Williams wrote:
In the 10.4 libkern/OSAtomic.h, OSAtomicDecrement32Barrier is defined as:
inline static int32_t OSAtomicDecrement32Barrier( int32_t *theValue )
while in the 10.5 libkern/OSAtomic.h, it's defined as:
inline static int32_t OSAtomicDecrement32Barrier( volatile int32_t *__theValue )
note the volatile qualifier on the parameter in the second case.
I don't claim to be an expert in it, but the second case certainly seems more correct. How you can do an atomic operation without volatile seems suspect at best.
But...my application is targeting 10.5, but it is picking up the 10.4 header. <pastedGraphic.tiff>
/Developer/SDKs/MacOSX10.4u.sdk/usr/include/libkern/OSAtomic.h
The include statement is simply:
#include <libkern/OSAtomic.h>
Any thoughts on why it might be picking up the 10.4 header? I've checked the various header search path build settings, but the only modifications to that are to point into my source tree - I certainly don't have the 10.4 SDK directory specified.
1) What does the Base SDK in your Target say? The target wins.
2) Do you have an Active SDK set in the toolbar or Active SDK menu? It trumps project settings.
Drag and drop the "Compiling" line for the source file that's doing that #include so we can see what it's actually being told to do.
Chris |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden