Late 2016 version of MAME (0.174) for libretro. Compatible with MAME 0.174 sets.
Go to file
2022-04-06 22:13:09 +02:00
3rdparty Fix build with GNU Make 4.3 2020-10-28 09:39:52 -03:00
android-project Cleanups and version bump 2016-05-25 08:19:21 +02:00
artwork -Added HQ2x, HQ3x and HQ4x shaders. [MooglyGuy,Jules Blok,Cameron Zemek,Maxim Stepin] 2016-04-18 19:40:07 +02:00
benchmarks fix building benchmarks (nw) 2016-03-08 13:09:32 +01:00
bgfx Equalized options of HLSL and BGFX HLSL chain 2016-05-05 20:59:33 +02:00
docs Normalized vector attenuation settings 2016-05-22 20:54:30 +02:00
doxygen Remove extraneous character (nw) 2016-03-16 19:30:11 -04:00
hash Change N64DD to use harddisk device instead of quikload device. 2016-05-25 16:38:47 -06:00
hlsl Normalized vector attenuation settings 2016-05-22 20:54:30 +02:00
ini/presets Normalized vector attenuation settings 2016-05-22 20:54:30 +02:00
keymaps Added README and LICENSE files (CC0) to folders containing meta-data or documentation (nw) 2016-03-05 10:31:41 +01:00
language Update for French/Belgian language files [Mevi] 2016-05-25 10:48:58 +02:00
metadata add compressed dats 2018-03-29 13:24:49 -04:00
nl_examples Implemented dynamic loading of precompiled solver code. [Couriersud] 2016-04-23 13:54:32 +02:00
plugins plugins/cheatfind: more (nw) 2016-05-03 09:39:16 -05:00
regtests Add some more per folder licenses (nw) 2016-03-05 10:56:44 +01:00
samples Added README and LICENSE files (CC0) to folders containing meta-data or documentation (nw) 2016-03-05 10:31:41 +01:00
scripts Fix build on Python 3.9+ 2021-12-06 11:24:27 -03:00
src Update libco 2022-04-06 22:13:09 +02:00
tests added attotime test for balrog (nw) 2016-03-18 14:00:16 +01:00
.gitattributes fix line endings for po files (nw) 2016-02-20 21:51:52 +01:00
.gitignore Initial work to make MAME work on Android [Miodrag Milanovic] 2016-03-27 17:35:23 +02:00
.travis.yml 6 is too many 3 is better, lets see about 4 (nw) 2015-12-12 14:50:03 -06:00
LICENSE.md (nw) 2016-03-30 19:08:33 -04:00
makefile Update makefile 2017-02-10 23:59:29 +01:00
Makefile.libretro Backport https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/libretrocores/lr-mame2016/01_disable_bgfx.diff 2019-07-08 17:38:41 +02:00
README.md Update README.md 2016-03-26 15:57:42 +01:00
uismall.bdf Use Adobe standard glyph names where possible 2016-03-21 02:47:12 +11:00

MAME

Join the chat at https://gitter.im/mamedev/mame

What is MAME?

MAME originally stood for Multiple Arcade Machine Emulator.

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 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

make

for a MAME build,

make SUBTARGET=arcade

for an arcade-only build, or

make SUBTARGET=mess

for MESS build.

For Linux users we have provided you with all the prerequisites.

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 vs2015

or use this command to build it directly using msbuild

make vs2015 MSBUILD=1

Where can I find out more?

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.

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.

License

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 Nicola Salmoria, and permission is required to use the "MAME" name, logo, or wordmark.

Copyright (C) 1997-2016  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
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
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 LICENSE.md for further details.