• 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: How does SDK Root affect compiles?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How does SDK Root affect compiles?


  • Subject: Re: How does SDK Root affect compiles?
  • From: Rick Mann <email@hidden>
  • Date: Tue, 20 Feb 2007 12:16:26 -0800


On Feb 20, 2007, at 08:44 , Chris Espinosa wrote:

Just one more reminder: you are pushing the edges of Xcode's limited support for alternate compilers, so this kind of thing is going to be difficult until we have a real extension API in place.

Yes, I realize that, and I'm doing my best to glean what I need to make it work. All that notwithstanding, in this case, this part of the build process is very much like a regular Xcode build, so I should be able to make it work.


Xcode has only a monolithic notion of SDKs. If an SDK is set, every path into /System, /Library, and /usr gets the SDKROOT prepended. You either have to copy the gdc pieces into a copy of the 10.4u SDK and point the SDKROOT to that, or move the gdc pieces out of /usr and supply custom paths to them that won't be modified.

There must be more going on than just this. If I don't include the SDK Path, I get fewer directories added to the call to gdc for linking. If I do include the path, I get a couple more directories (and all get prepended with the SDK Path, as one would expect). What I would expect is the same set of directories in both cases, just in one case they're all prepended with the SDK Path.


Moreover, I don't understand why gcc (remember, gdc is really just gcc) implicitly includes -lgphobos and -lgcc_eh when called plainly from the command line, but does not include these when called from Xcode. To make matters more confusing, if Xcode calls it with - isysroot (as a result of adding the SDK Path), gdc seems to implicitly include -lgcc_eh, but not -lgphobos (perhaps because of the missing gdc directory).

Finally, how does Xcode build the path "/Developer/SDKs/ MacOSX10.4u.sdk/usr/lib/gcc/darwin/gdc.0.17"? I get that the first part is the SDK Root, but from where does the second part come? Is it "/usr/lib/gcc/darwin/<.pbcompspec Version property>"?

TIA,
--
Rick


_______________________________________________ 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: 
 >How does SDK Root affect compiles? (From: Rick Mann <email@hidden>)
 >Re: How does SDK Root affect compiles? (From: Chris Espinosa <email@hidden>)

  • Prev by Date: Re: QuartzCore.framework on 10.3.9?
  • Next by Date: Re: Basic globals/extern question
  • Previous by thread: Re: How does SDK Root affect compiles?
  • Next by thread: Re: How does SDK Root affect compiles?
  • Index(es):
    • Date
    • Thread