• 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: Sending a build message less severe then #warning
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sending a build message less severe then #warning


  • Subject: Re: Sending a build message less severe then #warning
  • From: "Sean McBride" <email@hidden>
  • Date: Thu, 28 May 2009 11:13:50 -0400
  • Organization: Rogue Research Inc.

On 5/28/09 9:36 AM, Chris Jones said:

>> Which is a painful problem for those of us who want to use a compiler
>> that's not five years old... You simply *can't* use 4.3, 4.4, or 4.5 for
>> OS X (or iPhone) development.
>
>Am I missing something or doesn't the latest Xcode give you 4.2 as an
>option ? Still old but not as bad as 4.0...

You're right.  And 4.2 is 'only' 2 years old:
<http://gcc.gnu.org/gcc-4.2/>

Though Apple's fork surely has changes more recent.  It's just annoying
that there is a fork, and that changes from one take time to get to the
other (if at all).  I suspect that's what Gwynne's comment was about.

--
____________________________________________________________
Sean McBride, B. Eng                 email@hidden
Rogue Research                        www.rogue-research.com
Mac Software Developer              Montréal, Québec, Canada


 _______________________________________________
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

  • Follow-Ups:
    • Re: Sending a build message less severe then #warning
      • From: Gwynne Raskind <email@hidden>
References: 
 >Re: Sending a build message less severe then #warning (From: Sam Krishna <email@hidden>)
 >Re: Sending a build message less severe then #warning (From: Gwynne Raskind <email@hidden>)
 >Re: Sending a build message less severe then #warning (From: Chris Jones <email@hidden>)

  • Prev by Date: Re: Sending a build message less severe then #warning
  • Next by Date: Using target specific include paths
  • Previous by thread: Re: Sending a build message less severe then #warning
  • Next by thread: Re: Sending a build message less severe then #warning
  • Index(es):
    • Date
    • Thread