installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%

brew install mame

local Homebrew formula metadata

MacPortsvérifié · 94%

sudo port install mame

MacPorts ports tree · emulators/mame/Portfile · Source: api.github.com

Linux

Alpine Linux apkvérifié · 92%

sudo apk add mame

Alpine Linux edge package indexes · mame · Source: dl-cdn.alpinelinux.org

Debian aptvérifié · 92%

sudo apt install mame

Debian stable package indexes · mame · Source: deb.debian.org

Fedora dnfvérifié · 92%

sudo dnf install mame

Fedora Rawhide package metadata · mame · Source: dl.fedoraproject.org

Nixvérifié · 92%

nix profile install nixpkgs#mame

nixpkgs package indexes · pkgs/by-name/ma/mame/package.nix · Source: api.github.com

Arch Linux pacmanvérifié · 92%

sudo pacman -S mame

Arch Linux sync databases · mame · Source: geo.mirror.pkgbuild.com

openSUSE zyppervérifié · 92%

sudo zypper install mame

openSUSE Tumbleweed package metadata · mame · Source: download.opensuse.org

aperçu

Résumé du paquet

Multiple Arcade Machine Emulator

Liens du projet

Commandes et alias

mame

historique

Historique du projet et usages

MAME is a multi-purpose emulation framework whose stated purpose is to preserve decades of software history by documenting hardware and how it functions. Although originally the Multiple Arcade Machine Emulator, official documentation says it later absorbed sister projects and now covers arcade games, computers, consoles, calculators, and other vintage systems.

Historique du projet

MAME 0.1 was released on February 5, 1997. Early development moved quickly: MacMAME appeared in February 1997, X/MAME appeared in April 1997, vector-game support arrived in July 1997, and MAME32 also appeared in July 1997. The official history records a steady expansion from arcade CPU and sound emulation toward broader hardware documentation.

The project accumulated preservation infrastructure as it grew: CRCs for identifying ROMs in 1998, ZIP support in 1998, `history.dat` support in 1999, CHD support in 2002, and later major device-model and source-tree changes. In 2015 MESS merged into MAME, widening the project beyond arcade machines, and in 2016 MAME became GPL-2.0-or-later free and open source software with new documentation and licensing.

Historique d'adoption

MAME has had a broad cross-platform packaging history, with official Windows binaries and source releases, Unix-like ports, macOS variants, and package-manager entries across Homebrew, Debian, Fedora, Arch, Nix, MacPorts, Alpine, openSUSE, and others. The project history page explicitly treats supported ROM set growth as one measure of project success.

For users, adoption is tied less to a single GUI and more to the shared command-line executable and data formats. Front ends, ROM managers, preservation workflows, and downstream OS packages all orbit the same MAME release stream and compatibility expectations.

Modes d'utilisation

The ordinary package-manager workflow installs the `mame` executable, then users provide legally obtained ROM, disk, or media images separately. Official documentation emphasizes that copyrighted software images are not included and must be supplied by the user.

MAME reads configuration from INI search paths that differ by platform. Official command-line documentation lists default INI paths for Windows, macOS, and other platforms including Linux, making those paths important to packagers and users debugging why a setting is or is not being applied.

Pourquoi les passionnés de paquets s'y intéressent

MAME is package-manager lore because it is both an emulator and a preservation corpus interface. The package is just the executable and support files; the user's ROM sets, CHDs, artwork, plugins, shaders, and INI layers are separate data concerns.

For maintainers, MAME is a large C++ project with fast-moving compiler requirements, platform notes, bundled tools, and frequent releases. Small packaging differences around paths, SDL support, Lua/plugins, and INI locations can change user-visible behavior.

Chronologie

1997: MAME 0.1 released.
1998: MAME began using CRCs to identify ROMs and added built-in ZIP support.
2002: CHD support was introduced for hard-disk and other large media images.
2006: SDLMAME was released, improving Unix-like platform packaging.
2015: MESS merged into MAME.
2016: MAME became GPL-2.0-or-later free and open source software.

Related projects

MESS, the Multi Emulator Super System, was a sister project and was merged into MAME in 2015.
SDLMAME, MacMAME, MAME32, front ends, ROM managers, and MAME data files are part of the wider packaging and user ecosystem.

Sources

posture de sécurité

Niveau de risque : vert

narrow executable package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

narrow executable package without higher-risk signals

Signaux

metadata:no-higher-risk-signals

Comportement d'installation

Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
S’installe avec 9 dépendances d’exécution.
Les métadonnées de compilation listent 4 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Linux: ~/.mame/mame.ini./mame.ini./ini/mame.ini
macOS: ~/Library/Application Support/mame/mame.ini~/.mame/mame.ini./mame.ini./ini/mame.ini
Windows: ./mame.ini./ini/mame.ini./ini/presets/mame.ini

exécutables

Exécutables installés

Commande	Type	Exposition	Note
`mame`	cli	exécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-10

version du gestionnaire0.288

gestionnaire mis à jour2026-06-22

données localesOK

amontnot checked

dernière version détectéenon détecté

https://github.com/mamedev/mame

infoNo cached GitHub release or tag data was available.https://github.com/mamedev/mameconfiance none

métadonnées d'installation

Métadonnées du paquet

Clé du paquet	brew:mame
Version	0.288
Gestionnaire de paquets	Homebrew
Page du gestionnaire de paquets	https://formulae.brew.sh/formula/mame
Page d'accueil	https://mamedev.org/
Dépôt	https://github.com/mamedev/mame
Docs amont	https://docs.mamedev.org/
Licence	GPL-2.0-or-later
Archive source	https://github.com/mamedev/mame/archive/refs/tags/mame0288.tar.gz
Dernière mise à jour	2026-06-22T14:05:26-07:00
Pulse	updated
Dépendances	flac, jpeg-turbo, portaudio, portmidi, pugixml, sdl3, sqlite, utf8proc, zstd
Dépendances de compilation	glm, pkgconf, rapidjson, sphinx-doc
Bibliothèques fournies par macOS	expat
Bouteille	disponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrew	non défini
Service	aucun déclaré

faits du registre

Détails de la base source

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	mame
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Debian apt95%

mame 0.276+dfsg.1-1+deb13u1

Multiple Arcade Machine Emulator (MAME)

Installer mame avec Homebrew, apk, apt, dnf, MacPorts, Nix, pacman, zypper