I'm trying to use Xcode 1.5 to compile the MAME 0.86 source with the overrides from the earlier version of MacMAME. I know it won't compile cleanly, but I'm puzzled by the sheer number of errors it's giving me; for example, here are the first few errors I get when I try to compile 2100ops.c:
src/cpu/adsp2100/2100ops.c:60: error: parse error before "constants"
src/cpu/adsp2100/2100ops.c:66: warning: data definition has no type or storage class
src/cpu/adsp2100/2100ops.c: In function `set_mstat':
src/cpu/adsp2100/2100ops.c:86: error: `adsp2100' undeclared (first use in this function)
src/cpu/adsp2100/2100ops.c:88: error: `ADSPCORE' undeclared (first use in this function)
src/cpu/adsp2100/2100ops.c:88: error: parse error before "temp"
src/cpu/adsp2100/2100ops.c:90: error: `temp' undeclared (first use in this function)
The "parse error before 'constants'" is because "INT32" isn't defined anywhere. The other errors are also generated by things which aren't defined anyplace. This particular C code file has no #includes; it itself is #included from adsp2100.c, which defines the things it uses. I've never seen any other project where one .c file #includes another .c file; I figure that 2100ops.c itself isn't meant to be compiled.
The MAME 0.86 source distribution has no Makefile, per se: it has a "mame.mak", which references only object files (no C files), and a "rules.mak", which appears to reference every available C file (including 2100ops.c). So I haven't yet figured out how this is supposed to be able to compile on Windows, much less Mac.
I apologize for my utter cluelessness here. I'm trying to make sense of this so that I can reach a point where I can make a positive contribution, and until I get there I don't want to slow down anyone else who knows what he's doing.