How does the SDK selection affect my compiler settings?
How does the SDK selection affect my compiler settings?
- Subject: How does the SDK selection affect my compiler settings?
- From: James Bucanek <email@hidden>
- Date: Fri, 20 May 2005 10:04:33 -0700
I ran into something odd today.
I'm working on a Cocoa application that contained the following code
if ([[anItem title] isEqualToString:@"Save As…"])
I had been compiling this for months under Xcode 1.5/gcc 3, and for several weeks using Xcode 2.0/gcc 4.
Today, I decided to try cross-compiling the code using the 10.3.9 SDK. When I did, the file would no longer compile (I have "treat warnings as errors" set). I get the compiler error
warning: non-ASCII character in CFString literal
Here's the weird thing (to me, at least). If I select any regression SDK (10.2.8, 10.3.9, even 10.4.0) I get this warning. But if I switch to "Current Mac OS" the warning goes away.
So I have three questions:
1) How does the SDK selection affect the compiler behavior/flags?
2) Is there a gcc flag to ignore this warning? (It obviously isn't a limitation of the gcc 3 compiler, or the 10.3.x system as I've been building and running this same code under Xcode 1.5 & OS X 10.3 for months.) If there is such a switch, where the heck did you find it? ;) I've done every search I could think of, both on the gcc.gnu.org site, Apple's site, the gcc man pages, and the Internet in general.
3) Thinking that at some point I might need to include non-ASCII character in a literal CFString, how does one do it? I tried @"string\u2026", but got an error that unicode characters were only supported in C99. Can I use a UTF-8 sequence?
--
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