Re: No such file error?
Re: No such file error?
- Subject: Re: No such file error?
- From: "Sean McBride" <email@hidden>
- Date: Thu, 24 Nov 2005 10:26:40 -0500
- Organization: Rogue Research
On 2005-11-23 22:02, Scott Ribe said:
>> The double quotes made the difference.
>> I'll probably have to change < > to " " in other places also.
>
>FYI, roughly, the traditional meaning of <> vs "" is "system headers" vs
>"project headers". Of course sometimes when writing x-platform code, what is
>included in the "system" on some platform has to be added to some
>compatibility code directly in the project for other platforms. CW has a
>project option that blurs the distinction--convenient in some cases, but in
>others sets you up for unwittingly creating this problem.
And starting with 2.2, Xcode also (finally!) has this handy option, just
like CW does. From the release notes:
"Xcode now has a build setting, called "Always Search User
Paths" (ALWAYS_SEARCH_USER_PATHS), which causes #include <header.h>-
style directives to always search user paths (those defined in "User
Header Search Paths" (USER_HEADER_SEARCH_PATHS)) before the standard
paths (those defined in "Header Search Paths" (HEADER_SEARCH_PATHS)). If
this setting is disabled, only #include "header.h"-style directives will
search the user paths. This setting is enabled by default for backwards
compatibility."
--
____________________________________________________________
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