• 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: Was : Re: Garbage collection in XCode 2.1, and Cocoa - now compiler options
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Was : Re: Garbage collection in XCode 2.1, and Cocoa - now compiler options


  • Subject: Re: Was : Re: Garbage collection in XCode 2.1, and Cocoa - now compiler options
  • From: Andrew Satori <email@hidden>
  • Date: Thu, 28 Jul 2005 15:28:33 -0400

I believe the official line is that they are not 'stable' so the documents have not been made public.

That said, there is a hidden gotcha. so long as your compiler is derived from one of the shipped compilers you are in good shape, but if you need to declare an entirely new compiler (eg, mcs for Mono & C#, which I've been working on for over a year in fits and starts), you have to add a plugin, and while many of the plist formats are very straightforward, classdumping the existing plugins and trying to reverse the interface has been unsuccessful to this point (though admittedly it's only been a half assed effort on my part).

Andy

On Jul 28, 2005, at 3:12 PM, J.M. Brough wrote:


On 28 Jul 2005, at 16:38, Chris Espinosa wrote:


Our architecture is that for each tool there is a specification plist that has entries for each compiler switch, giving it a human- readable name, a short description, a build setting variable, a manner to display it in the inspector (check box, string, popup), and a default value. It's pretty easy, when we hear about a new compiler flag, to create this plist to keep them in sync; I added three or four for Intel support in a matter of minutes.



Chris

Interesting...

When myself and a few others requested info on these few minute changes we rx no response. I asked for doc links, not a how to. Yet, no response. If it is so simple and easy when you know. Please explain why this info is not more generally available.

Luckily, another xcode-user replied off-list and gave me a serious head start. (Thanks Brandon)

Cheers,

Jason.

 _______________________________________________
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

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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: 
 >Re: Garbage collection in XCode 2.1, and Cocoa (From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>)
 >Re: Garbage collection in XCode 2.1, and Cocoa (From: Chris Espinosa <email@hidden>)
 >Was : Re: Garbage collection in XCode 2.1, and Cocoa - now compiler options (From: "J.M. Brough" <email@hidden>)

  • Prev by Date: Re: Three x-code 2.1 bugs?
  • Next by Date: Re: XCode editor intolerably slow
  • Previous by thread: Was : Re: Garbage collection in XCode 2.1, and Cocoa - now compiler options
  • Next by thread: Re: Was : Re: Garbage collection in XCode 2.1, and Cocoa - now compiler options
  • Index(es):
    • Date
    • Thread