• 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 the SDK selection affect my compiler settings?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How does the SDK selection affect my compiler settings?


  • Subject: Re: How does the SDK selection affect my compiler settings?
  • From: James Bucanek <email@hidden>
  • Date: Sat, 21 May 2005 08:09:34 -0700

Chris Espinosa wrote on Friday, May 20, 2005:

>
>On May 20, 2005, at 2:55 PM, James Bucanek wrote:
>
>> So I wonder why the compiler behaviour changes when I link against
>> and SDK?  A quick grep shows that there are a bunch of statements like
>>
>>     #pragma warning ( disable: 4244 )
>>
>> scattered all over the system headers.  I'm wondering if one of
>> those is causing this particular warning to be set in the
>> compiler.  Of course, since I can't seem to find any kind of
>> comprehensive list of warning numbers for gcc, I have no idea which
>> one might do that.
>>
>
>These are actually in the 10.3.9 system headers, in the open source
>project GLUT:
>
<clip>
>
>They are not for gcc. I see these wrapped in an #ifdef:
>
>#if defined(_WIN32)
>#include <windows.h>
>#pragma warning (disable:4244)          /* disable bogus conversion
>warnings */
>#endif
>
>So do you have any idea why _WIN32 might be getting defined in your
>build?  There's no place in Apple headers or SDKs where this is
>defined, and gcc doesn't define this macro.

No, I wasn't saying that these are getting executed.  All I did was grep all of the SDK headers looking for anything that might change the warnings issued by the compiler.  These #pragmas were the only thing that looked suspicious.

So we're still back to the question of why the compiler acts differently when I select a different SDK.  Even more curious, why does it spit out warnings when I compile against 10.4.0 and compiles fine when I compile against "Current Mac OS"?

Note that I'm not going to investigate this further, I just find it interesting.  I've already worked around the warnings in my current code, and Chris has provided me with a way of inserting unicode NSString constants should I need that in the future.

"It's a mystery." -- Geoffrey Rush, Shakespeare in Love

--
James Bucanek <mailto:email@hidden>
 _______________________________________________
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: How does the SDK selection affect my compiler settings? (From: Chris Espinosa <email@hidden>)

  • Prev by Date: strip -R not working on GCC 4 generated binaries?
  • Next by Date: Re: strip -R not working on GCC 4 generated binaries?
  • Previous by thread: Re: How does the SDK selection affect my compiler settings?
  • Next by thread: Re: How does the SDK selection affect my compiler settings?
  • Index(es):
    • Date
    • Thread