mame/README.md
sonninnos d585252673 MAME 0.263
-----BEGIN PGP SIGNATURE-----
 
 iQIzBAABCAAdFiEE0DYtsBhE4EM627+6wXSxAYxAcQ4FAmXd0vMACgkQwXSxAYxA
 cQ5B8BAAiE+wyJ9vr5mscrzwZvfnEAWgPZxCqBQ9jyXL+Tz9yyQAij9iyIHz+14N
 Oe27Z04a0byKU+MNal74ap2c90Fz39cnABbcSl0n20TCMBs4Xfw1sldbURwLuJdG
 bowru+WebAzu1qgKAe71/PvUFniws+RbVF3dqCXhHEKjMgQmbbTLscfyU3IsXD3Y
 hiEoBXdUY+z+91BQgcjEtTqj2UqiBr0ePnRkyul1RhQI0GfndGqSXtW0/LnmscBb
 aBPbT4GiH1/a5Tq7AUmIQJkHHvCNhgFRDszgKBUWqSjOqYoCx08ZBel/fj76a820
 LqUlapSPScsVdSlUGZdhvhm8ZNdIzkX2ST+k5HILm0/vlCskfsK78ax8f9rJoOII
 DOVPU/EXmEVXTzImBjW1EWTFSgSpQ5zDQ8JqGXacTDrf5msQ0RAwtGMPuEkp9w2Y
 2uH8atN7Z+tYRDtPDhAHuRgvuvq5HrFqZZRNSjohwx2RTv/ye7vqdmWxzGF54+mw
 efPKQabagKSgQK4i8GH8nIHLSgvy2Xk0JwWjc7l7BueU1FtzEAQ1ajbsbyXJyhRg
 oV04FJx5QXJhptFreMkyKWobiXtjfYLK39lwLNiaKlpPuQrjo2IWsy+Bd015KGgo
 Kv3jtbGwXhPulyVU3O7bwuF3QP35SD/hjTYi90vSJbVvi1HCP30=
 =V7N9
 -----END PGP SIGNATURE-----

Merge tag 'mame0263' of https://github.com/mamedev/mame into 0263

MAME 0.263
2024-02-28 17:47:43 +02:00

6.6 KiB

pipeline status

Libretro notice

Before sending bug reports to the upstream bug tracker, make sure the bugs are reproducible in the latest standalone release.

To build libretro MAME core from source you need to use Makefile.libretro make file:

make -f Makefile.libretro

For faster building after the initial makefile creation:

make -f Makefile.libretro PREMAKE=0

For Windows install lld for much faster linking.


MAME

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

Continuous integration build status:

OS/Compiler Status
Linux/clang and GCC CI (Linux)
Windows/MinGW GCC and clang CI (Windows)
macOS/clang CI (macOS)
UI Translations Compile UI translations
Documentation Build documentation
BGFX Shaders Rebuild BGFX shaders

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 UNIX-like system (including Linux and macOS), it could be as easy as typing

make

for a full build,

make SUBTARGET=tiny

for a build including a small subset of supported systems.

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

For recent versions of macOS 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 vs2019

or use this command to build it directly using msbuild

make vs2019 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 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.

See more specific C++ Coding Guidelines on our documentation web site.

License

The MAME project as a whole is made available 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 the source files (over 90% including core files) are made available under the terms of the 3-clause BSD License, and we would encourage new contributors to make their contributions available under the terms of 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-2024  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 version 2, as provided in
docs/legal/GPL-2.0.

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.

Please see COPYING for more details.