kexts built with XCode 2.1 & 2.2
kexts built with XCode 2.1 & 2.2
- Subject: kexts built with XCode 2.1 & 2.2
- From: david tay <email@hidden>
- Date: Thu, 3 Nov 2005 14:20:24 -0800
Hi,
I've been testing out the latest releases of darwin sources for some
kexts with XCode 2.1 & 2.2.
The sources build fine with both XCode 2.1 and 2.2. However, when
attempting to kextload (on PPC), the kext built with XCode 2.2 fails
to load with a message like
22AppleEHCIedMemoryBlock is not compatible with its superclass,
24IOBufferMemoryDescriptor superclass changed?
kextload: a link/load error occured for kernel extension
AppleUSBEHCI.kext
load failed for extension AppleUSBEHCI.kext
I guessing that this a known issue. Should I simply use XCode 2.1 and
forget about XCode 2.2?
Also, how should people outside Apple deal with the demise of
AbsoluteTime and the various clock macros in Tiger? I'm currently
keeping the definitions (taken from 10.3.9) in a separate .h file and
#including that file where those macros/ definitions are used. I know
that AbsoluteTime is still used in a number of locations in the
system and that some system calls have to be made with AbsoluteTime.
I have to build kexts that run on 10.3.9, 10.4.x and possibly intel
macs.
Is there a better way than using a separate .h file or attempting not
to use AbsoluteTime?
From what I've experienced thus far, it seems safer for me to keep
my development and build systems on 10.3.9 so that I can avoid the
hassle of
a. having kextload issues caused by newer releases of XCode.
b. working around the demise of AbsoluteTime and associated clock
macros while maintaining the same code base.
Are there any suggestions on how I could resolve the 2 issues other
than remaining on 10.3.9?
Thanks,
David
_______________________________________________
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