On Aug 25, 2004, at 8:57 PM, Shawn Erickson wrote:
On Aug 25, 2004, at 9:09 AM, Massimo Marino wrote:
Is not an issue when compiling in the terminal.
So what are the difference between how you are calling gcc and how
xcode is calling gcc. You can see what xcode is doing if you open the
build window ("Detailed Build Results") and pull up the slider at the
bottom (second from the bottom in 1.5) to show what calls it actually
is doing.
currently the only workaround I have found is to copy /usr/include
header files referenced by system files locally. Xcode then finds them
instead of digging (without any -I<path> to those files) in the project
files with same names (although starting with a capital letter, as in
SealBase/Time.h).
Frankly, not kosher.
Massimo
_______________________________________________
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.
