|
|
Re: Faster MAMEhub released and our new web site
09/07/11 08:41 AM
|
|
|
> Fair warning: on 64-bit, MSVC produces a slower MAME binary than MinGW (32-bit it
> depends on the specific driver - each compiler's faster on some specific games), and
> MAME is not QA'ed for non-MinGW compilers so any bugs found in that configuration are
> invalid for MAMETesters.
>
> In other words, yet again someone assumed MAMEdev are a bunch of stupids who "durr"ed
> our way to emulating 7000 games. Not so, we do actively work at this stuff ;-)
I don't think that MAMEdev are a bunch of stupids, but I think that MAMEdev are xenophobic and use outdated build tools.
If MAME isn't QA'ed for MSVC, why is the first developer doc on mamedev.org "Building MAME using Microsoft Visual Studio compilers"?
I am almost done with my own version of the MAME build system that links WAY faster (read: static libraries), breaks ridiculous dependency cycles (src/emu depended on drivlist.c which depended on drivers which depended on src/emu), and separates building tools like mk68kmake from building the emulator itself. With these changes and some wrapper code, I can compile and run the latest MAME on Android and Google Native Client.
Check out MAMEHub here: http://www.mamehub.info/
|
|
Index 
Flat 
Re: Faster MAMEhub released and our new web site
Reply
