• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Building Universal IOKit Drivers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building Universal IOKit Drivers


  • Subject: Re: Building Universal IOKit Drivers
  • From: Eric Albert <email@hidden>
  • Date: Tue, 25 Apr 2006 02:09:44 +0200

On Apr 24, 2006, at 11:45 PM, Chris Cooksey wrote:

I sent this to the darwin drivers list, but I realize now that this is definitely an Xcode question:

I am trying to build universal IOKit KEXTs on a PowerPC machine using Xcode 2.2.1.

I have set up the properties meticulously according to the Technote that describes the process:

GCC_VERSION_i386 = 4.0
GCC_VERSION_ppc = 3.3
MACOSX_DEPLOYMENT_TARGET_i386 = 10.4
MACOSX_DEPLOYMENT_TARGET_ppc = 10.2
SDKROOT_i386 = /Developer/SDKs/MacOSX10.4u.sdk
SDKROOT_ppc = /Developer/SDKs/MacOSX10.2.sdk

and I have applied all the other recommended changes as well. I have been through it several times. I am sure I haven't missed anything.

The PowerPC half builds fine. But when I try to build the Intel half I get this message:

/System/Library/Frameworks/Kernel.framework/PrivateHeaders/ architecture/byte_order.h:37:42: error: architecture/i386/ byte_order.h: No such file or directory

and a bunch of others.

Looking at the command used by Xcode to build one of the files, I see the following option:

-I/System/Library/Frameworks/Kernel.framework/PrivateHeaders

This is the problem. If I copy the command to the terminal and remove the above include path, the file in question will compile. (In fact, if I compile every file manually, I can actually build my project).

So my questions are: how did that path get put on the command line, and how do I get rid of it? I am not specifying it anywhere -it would appear to be something Xcode is adding.

Apparently Xcode adds that path for various complicated internal-to- Apple reasons, but normally it shouldn't affect anything. The bigger question is why you have a PrivateHeaders in the first place. Have you installed headers from Darwin or something like that?


I'd suggest moving /System/Library/Frameworks/Kernel.framework/ PrivateHeaders aside and seeing what happens.

Hope this helps,
Eric

_______________________________________________
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


References: 
 >Building Universal IOKit Drivers (From: Chris Cooksey <email@hidden>)

  • Prev by Date: Re: NSCFDictionary EXCEPTION
  • Next by Date: Re: NSCFDictionary EXCEPTION
  • Previous by thread: Re: Building Universal IOKit Drivers
  • Next by thread: Re: Building Universal IOKit Drivers
  • Index(es):
    • Date
    • Thread