[lcampbell]

How can I get gcc NOT to search /System/Library/Frameworks/foo.framework/Headers when I say #include <foo/gargle.h>?

-nostdinc doesn't do it.

It seems that the preprocessor is searching the frameworks headers first, even before any directories I specified with -I. So far the only way I've found to prevent framework headers from being found is to rename or delete them. This is ugly.

If you want to include gargle.h in a directory foo in the directory in which the c source file containing the #include directive, you'd want to use

#include "foo/gargle.h"

When you use <...> around the header file name, gcc _always_ searches the standard header file location.
When you use "..." gcc searches for the file specified relative to the source file.

Hope that helps you a little.

[lcampbell]

Yeah, but there are political reasons it's difficult for me to change the source. In "normal" (i.e., all other) compilers, the -I command line option inserts the specified directory at the FRONT of the list of "system places" to search. But not on MacOS X. Frameworks are ALWAYS searched first, followed by -I directories, followed by the "other" system places (/usr/include). This is wrong.