Re: Relative paths
Re: Relative paths
- Subject: Re: Relative paths
- From: Alastair Houghton <email@hidden>
- Date: Fri, 20 Feb 2004 12:20:52 +0000
On 19 Feb 2004, at 22:58, Patrick Coskren wrote:
> On Feb 19, 2004, at 5:38 PM, Mark Lentczner wrote:
>
>> Many compilers have switches (perhaps on by default) that treat <...>
>> and "..." exactly the same.
>
> As far as I can tell, XCode doesn't (though I'd love to hear
> differently). What's surprising to me is that if I put my source
> directory on the system include directory list, "../../" doesn't seem
> to work as a header file path. Hopefully I'm doing something wrong.
> But perhaps it's a big or even a feature.
I think you might want -I. (or just add "." to the list of include
paths).
BTW, the code might not be wrong exactly. There are some portability
problems wrt. include path searching, in particular I seem to recall
that ANSI and traditional compilers search in different directories
when you #include a file from another #included file and use the quote
syntax. I can't remember all of the details of the problems you can
encounter, but it wouldn't surprise me if the use of <> rather than ""
was a deliberate attempt to straighten them out.
Kind regards,
Alastair.
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.