| 3rdparty | ||
| artwork | ||
| docs | ||
| hash | ||
| hlsl | ||
| keymaps | ||
| nl_examples | ||
| scripts | ||
| src | ||
| web | ||
| .gitattributes | ||
| .gitignore | ||
| makefile | ||
| mame.doxygen | ||
| README.md | ||
MAME
What is MAME?
MAME stands for Multiple Arcade Machine Emulator.
MAME's purpose is to preserve decades of video-game history. As gaming technology continues to rush forward, MAME prevents these important "vintage" games from being lost and forgotten. This is achieved by documenting the hardware and how it functions. The source code to MAME serves as this documentation. The fact that the games are playable serves primarily to validate the accuracy of the documentation (how else can you prove that you have recreated the hardware faithfully?).
What is MESS?
MESS (Multi Emulator Super System) is the sister project of MAME. MESS documents the hardware for a wide variety of (mostly vintage) computers, video game consoles, and calculators, as MAME does for arcade games.
The MESS and MAME projects live in the same source repository and share much of the same code, but are different build targets.
How to compile?
If you're on a *nix system, it could be as easy as typing
make
for a MAME build,
make SUBTARGET=arcade
for an arcade-only build, or
make SUBTARGET=mess
for a MESS build (provided you have all the prerequisites).
For Windows users, we provide a ready-made build environment based on MinGW-w64. Visual Studio builds are also possible.
Where can I find out more?
- Official MAME Development Team Site (includes binary downloads for MAME and MESS, wiki, forums, and more)
- Official MESS Wiki
- MAME Testers (official bug tracker for MAME and MESS)
Contributing
Coding standard
MAME source code should be viewed and edited with your editor set to use four spaces per tab. Tabs are used for initial indentation of lines, with one tab used per indentation level. Spaces are used for other alignment within a line.
Some parts of the code follow GNU style; some parts of the code follow K&R style -- mostly depending on who wrote the original version. Above all else, be consistent with what you modify, and keep whitespace changes to a minimum when modifying existing source. For new code, the majority tends to prefer GNU style, so if you don't care much, use that.