> I don't think that MAMEdev are a bunch of stupids, but I think that MAMEdev are
> xenophobic and use outdated build tools.
We'd love to update the build tools, but there's a blocker bug in MinGW-W64 with C++ try/catch handling that renders MAME unusable. (Yes, we've filed an official bug with them).
I'm fuzzy how a project which regularly includes submissions from 4 continents is "xenophobic".
> If MAME isn't QA'ed for MSVC, why is the first developer doc on mamedev.org "Building
> MAME using Microsoft Visual Studio compilers"?
Because that's a non-obvious process, so it needs documentation.
> I am almost done with my own version of the MAME build system that links WAY faster
> (read: static libraries)
MAME has built static libraries since the beginning of time and it frankly hasn't done much for link times.
>, breaks ridiculous dependency cycles (src/emu depended on
> drivlist.c which depended on drivers which depended on src/emu)
That's not a build system thing, that's a "someone go through and clean up the #include graph" thing
> , and separates
> building tools like mk68kmake from building the emulator itself.
Those *are* separate - we've supported cross-compiles in the build system for 2 or 3 years now.
I do hope your miracle new setup uses Cmake though. I'm a fan, we use it at work.
> With these changes
> and some wrapper code, I can compile and run the latest MAME on Android and Google
> Native Client.
Google, Inc. has done an official port of MAME to NaCl, and those changes have been quietly folded back into mainline over the last several releases so I would certainly hope you can do that.