Re: Source Tree Preference
Re: Source Tree Preference
- Subject: Re: Source Tree Preference
- From: Scott Tooker <email@hidden>
- Date: Sun, 9 Nov 2003 16:03:39 -0800
By default, gcc looks in /usr/include, so
#include <limits.h>
will pick up /usr/include/limits.h, but
#include <sys/types.h>
will pick up /usr/include/sys/types.h
Scott
On Nov 9, 2003, at 1:01 PM, Marshall Clow wrote:
>> Such things work on simplistic systems, only. Take the file
>> "limits.h", for example:
>>
>> Nobile:~$ find /usr/include -name limits.h -print
>> /usr/include/gcc/darwin/2.95.2/machine/limits.h
>> /usr/include/gcc/darwin/3.1/machine/limits.h
>> /usr/include/gcc/darwin/3.3/machine/limits.h
>> /usr/include/i386/limits.h
>> /usr/include/limits.h
>> /usr/include/machine/limits.h
>> /usr/include/ppc/limits.h
>>
>> Which one should the compiler use by default? There are already some
>> rules and more rules whould make things more complicated (and break
>> compatibility to most other UNIces in the world).
>
> And how does the compiler know which one to use now?
> if I say "#include <limits.h>, which one gets included?
>
> FWIW, If I tell CW to look in "/usr/include/" (recursively), it will
> read "/usr/include/limits.h".
[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.