Re: <types.h> and other includes
Re: <types.h> and other includes
- Subject: Re: <types.h> and other includes
- From: Markian Hlynka <email@hidden>
- Date: Wed, 23 Feb 2005 00:43:49 -0700
On Feb 22, 2005, at 22:36, Jeff Laing wrote:
1. I had to add #include <stdlib.h> to a file when using the makefile,
because it didn't know what exit() was. Why didn't xcode have a
problem
with this? If xcode has a bunch of automatic includes, is it feasible
to disable them so I get the same errors for inclusion as I would when
running make? And, if this was an xcode thing, why didn't gcc/make on
OS X have trouble with this?
My guess is that your project has a pre-compiled header enabled, but
your
makefiles don't.
I think I know what you mean, but I think I haven't stated things
clearly:
Xcode:
Builds fine, no extra includes required
gcc/make OS X
Builds fine, no extra includes required
gcc/mak linux:
needs extra includes explicitly added.
So, if it was just Xcode, I'd say you were right. But, since make
behave the same way as Xcode on OS X, could this still be a possible
reason?
As David said:
Not sure what functions you called but in C all functions without
prototypes are
assumed to exist and return "int".
Not sure why u_int16_t would be defined by default... Some automatic
Framework includes perhaps?
I realize that undefined functions get int return types. But, of the
above configs, it was the linux one that didn't know what 'exit' was.
It's a little different for the u_int16_t, but even so, I didn't
include any Frameworks in my OS X makefile... are these things included
automatically?
Markian
_______________________________________________
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