From what I can tell, the source of the problem is what Apple calls
"toll-free" bridging, which is cast-equivalency between C-language Core Foundation datatypes (most of which start with CF) and their Foundation Kit (objective-c) equivalents.
Whether it's proper or not (and I agree that there seems to be some over-reaching in the headers), it's what I need to be able to do. Thus, it seems that there ought to be a way to specify an option for the compile phase and not linking. Truth be told, it's only really necessary for backend.cmod, but that's probably beside the point.
It seems incorrect that where would be various sets of flags (CPPFLAGS, DEFINS and CFLAGS) that all end up being used as part of what is very obviously not a compilation command. After all, LDFLAGS don't end up on the compilation lines, right?
Bill
On Wed, 21 Dec 2011, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
Including a header with obj-c syntax from C does not sound like a legitimate thing to do to me. The other way around would probably be legit. If the API is C, it should be defined in header files which are C.