ARCADE32/64 - MAME with working arcade games only
C++ Lua C Python Scala GLSL Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
3rdparty taptun: add support for Windows (#3790) Jul 30, 2018
android-project version bump (nw) Jul 24, 2018
artwork move some content for release archive out of build repo into main repo Aug 14, 2017
benchmarks Updates "2017" strings to "2018" where relevant. Jan 5, 2018
bgfx Updated GENie, BGFX, BX, added BIMG since it is separated now, update… Dec 1, 2017
ctrlr move some content for release archive out of build repo into main repo Aug 14, 2017
docs Merge remote-tracking branch 'upstream/master' Aug 12, 2018
doxygen doc: update MAME short description (nw) Nov 5, 2017
hash pc98.xml: softlist updates, part 2 (A) (#3855) Aug 15, 2018
hlsl 0.193 release files Dec 27, 2017
ini/presets Revert "New phosphor persistence shaders for HLSL" Jan 5, 2017
keymaps fix some typos (#2772) Nov 3, 2017
language Created a full Norwegian translation Aug 5, 2018
nl_examples Doxygen work. How the heck can one enforce a consistent device Feb 5, 2017
plugins hiscore.dat: Updates [Leezer] Jul 15, 2018
projects Enable building projects that are separate of MAME but use same core … Dec 8, 2016
regtests fix some typos (#2772) Nov 3, 2017
roms Restore this, it's used when building packages (nw) Oct 24, 2017
samples move some content for release archive out of build repo into main repo Aug 14, 2017
scripts * (nw) Aug 16, 2018
src Merge remote-tracking branch 'upstream/master' Aug 16, 2018
tests Updates "2017" strings to "2018" where relevant. Jan 5, 2018
web Updates "2017" strings to "2018" where relevant. Jan 5, 2018
.appveyor.yml Rename appveyor.yml Jul 7, 2018
.drone.sec [skip CI] Add irc bot notification for tea-ci (nw) May 29, 2016
.drone.yml Can tea-ci build tools? Jul 8, 2016
.gitattributes move some content for release archive out of build repo into main repo Aug 14, 2017
.gitignore move some content for release archive out of build repo into main repo Aug 14, 2017
.travis.yml Update .travis.yml Jul 22, 2017 missed one, sorry *nw* Aug 25, 2017 cherry-pick fixes from mainline and clean up some stuff (nw) Jul 23, 2018
dist.mak add a clean target to dist.mak, mark targets phony (nw) Aug 14, 2017
makefile make rectangle work better with constexpr, change many things to use … Jul 27, 2018
uismall.bdf Updates "2017" strings to "2018" where relevant. Jan 5, 2018


Join the chat at

Build status for tiny build only, containing just core parts of project:

OS/Compiler Status
Linux GCC / OSX Clang Build Status
Windows MinGW Build Status
Windows MSVC Build status

Static analysis status for entire build (except for third-party parts of project):

Coverity Scan Status

What is MAME?

MAME is a multi-purpose emulation framework.

MAME's purpose is to preserve decades of software history. As electronic technology continues to rush forward, MAME prevents this important "vintage" software 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 software is usable serves primarily to validate the accuracy of the documentation (how else can you prove that you have recreated the hardware faithfully?). Over time, MAME (originally stood for Multiple Arcade Machine Emulator) absorbed the sister-project MESS (Multi Emulator Super System), so MAME now documents a wide variety of (mostly vintage) computers, video game consoles and calculators, in addition to the arcade video games that were its initial focus.

How to compile?

If you're on a *NIX or OSX system, it could be as easy as typing


for a MAME build,

make SUBTARGET=arcade

for an arcade-only build, or

make SUBTARGET=mess

for MESS build.

See the Compiling MAME page on our documentation site for more information, including prerequisites for Mac OS X and popular Linux distributions.

For recent versions of OSX you need to install Xcode including command-line tools and SDL 2.0.

For Windows users, we provide a ready-made build environment based on MinGW-w64.

Visual Studio builds are also possible, but you still need build environment based on MinGW-w64. In order to generate solution and project files just run:

make vs2017

or use this command to build it directly using msbuild

make vs2017 MSBUILD=1

Where can I find out more?


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 Allman 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 Allman style, so if you don't care much, use that.

All contributors need to either add a standard header for license info (on new files) or inform us of their wishes regarding which of the following licenses they would like their code to be made available under: the BSD-3-Clause license, the LGPL-2.1, or the GPL-2.0.


The MAME project as a whole is distributed under the terms of the GNU General Public License, version 2 or later (GPL-2.0+), since it contains code made available under multiple GPL-compatible licenses. A great majority of files (over 90% including core files) are under the BSD-3-Clause License and we would encourage new contributors to distribute files under this license.

Please note that MAME is a registered trademark of Gregory Ember, and permission is required to use the "MAME" name, logo, or wordmark.

Copyright (C) 1997-2018  MAMEDev and contributors

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
GNU General Public License for more details.

You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Please see for further details.