MAME:Installing - Revision history

Johnnyo: /* 1. Get MAME */ make the items as the lists

2026-06-02T20:55:08Z

1. Get MAME: make the items as the lists

← Older revision		Revision as of 21:55, 2 June 2026
Line 21:		Line 21:
	Alternatively, for the MAME platform as a whole, you can also check your package manager, or [https://docs.mamedev.org/initialsetup/compilingmame.html build from sources].		Alternatively, for the MAME platform as a whole, you can also check your package manager, or [https://docs.mamedev.org/initialsetup/compilingmame.html build from sources].

	Git of official MAME: [https://github.com/mamedev/mame/ https://github.com/mamedev/mame/]		* Git of official MAME: [https://github.com/mamedev/mame/ https://github.com/mamedev/mame/]

	Git of Holub's fork: [https://github.com/holub/mame https://github.com/holub/mame] (may contain extra fixes and features before they are merged to official repository, from the Actions page, if you're logged in, the most recent executables could be downloaded).		* Git of Holub's fork: [https://github.com/holub/mame https://github.com/holub/mame] (may contain extra fixes and features before they are merged to official repository, from the Actions page, if you're logged in, the most recent executables could be downloaded).

	=== 2. Get TBBLUE (the Next 'boot ROM') ===		=== 2. Get TBBLUE (the Next 'boot ROM') ===

Johnnyo: /* Installation */ removed links to the single cpp source, not needed in the intro

2026-06-02T20:54:29Z

Installation: removed links to the single cpp source, not needed in the intro

← Older revision		Revision as of 21:54, 2 June 2026
Line 21:		Line 21:
	Alternatively, for the MAME platform as a whole, you can also check your package manager, or [https://docs.mamedev.org/initialsetup/compilingmame.html build from sources].		Alternatively, for the MAME platform as a whole, you can also check your package manager, or [https://docs.mamedev.org/initialsetup/compilingmame.html build from sources].

	Git of official MAME: [https://github.com/mamedev/mame/ https://github.com/mamedev/mame/~~] [https://github.com/mamedev/mame/blob/master/src/mame/sinclair/next/specnext.cpp specnext.cpp~~]		Git of official MAME: [https://github.com/mamedev/mame/ https://github.com/mamedev/mame/]

	Git of ~~holub~~'s fork: [https://github.com/holub/mame https://github.com/holub/mame~~] [https://github.com/holub/mame/blob/master/src/mame/sinclair/next/specnext.cpp specnext.cpp~~] (may contain extra fixes and features before they are merged to official repository, from the Actions page, if you're logged in, the most recent executables could be downloaded).		Git of Holub's fork: [https://github.com/holub/mame https://github.com/holub/mame] (may contain extra fixes and features before they are merged to official repository, from the Actions page, if you're logged in, the most recent executables could be downloaded).

	=== 2. Get TBBLUE (the Next 'boot ROM') ===		=== 2. Get TBBLUE (the Next 'boot ROM') ===

Johnnyo: /* Installation */ the Actions page in the first mention

2026-06-02T20:52:17Z

Installation: the Actions page in the first mention

← Older revision		Revision as of 21:52, 2 June 2026
Line 23:		Line 23:
	Git of official MAME: [https://github.com/mamedev/mame/ https://github.com/mamedev/mame/] [https://github.com/mamedev/mame/blob/master/src/mame/sinclair/next/specnext.cpp specnext.cpp]		Git of official MAME: [https://github.com/mamedev/mame/ https://github.com/mamedev/mame/] [https://github.com/mamedev/mame/blob/master/src/mame/sinclair/next/specnext.cpp specnext.cpp]

	Git of holub's fork: [https://github.com/holub/mame https://github.com/holub/mame] [https://github.com/holub/mame/blob/master/src/mame/sinclair/next/specnext.cpp specnext.cpp] (may contain extra fixes and features before they are merged to official repository)		Git of holub's fork: [https://github.com/holub/mame https://github.com/holub/mame] [https://github.com/holub/mame/blob/master/src/mame/sinclair/next/specnext.cpp specnext.cpp] (may contain extra fixes and features before they are merged to official repository, from the Actions page, if you're logged in, the most recent executables could be downloaded).

	=== 2. Get TBBLUE (the Next 'boot ROM') ===		=== 2. Get TBBLUE (the Next 'boot ROM') ===

Johnnyo: /* Continuous Integration MAME Builds */ Actions

2026-06-02T20:43:54Z

Continuous Integration MAME Builds: Actions

← Older revision		Revision as of 21:43, 2 June 2026
Line 162:		Line 162:
	MAME is updated on a release schedule, but due to the ongoing nature of development, including for the MAME Next machine, it can sometimes be useful to install a more recent build if it contains a new feature or bugfix you are interested in. Sometimes, this ongoing work is discussed on social media, such as the [https://discordapp.com/channels/556228195767156758/752197165891321886 Next Developer Discord].		MAME is updated on a release schedule, but due to the ongoing nature of development, including for the MAME Next machine, it can sometimes be useful to install a more recent build if it contains a new feature or bugfix you are interested in. Sometimes, this ongoing work is discussed on social media, such as the [https://discordapp.com/channels/556228195767156758/752197165891321886 Next Developer Discord].

	Continuous Integration (CI) builds are available from both :		Continuous Integration (CI) builds are available from the GitHub Action pages of both:

	* the [https://github.com/mamedev/mame/actions https://github.com/mamedev/mame/actions -- primary MAME repo Actions pagee] and		* the [https://github.com/mamedev/mame/actions https://github.com/mamedev/mame/actions -- primary MAME repo Actions pagee] and
Line 174:		Line 174:
	To try out a CI build (more precisely, the resulting binary executable, which is a produced "artifact" of the build process) , first do a full MAME install from the [https://www.mamedev.org/release.html latest release] if you have not already done so. Then back up your main binary from its installation location - these are called something like <code>mame.exe</code> or <code>mame</code>. You're backing it up to be able to restore it if the CI build doesn't work, or if you don't like how the CI build behaves.		To try out a CI build (more precisely, the resulting binary executable, which is a produced "artifact" of the build process) , first do a full MAME install from the [https://www.mamedev.org/release.html latest release] if you have not already done so. Then back up your main binary from its installation location - these are called something like <code>mame.exe</code> or <code>mame</code>. You're backing it up to be able to restore it if the CI build doesn't work, or if you don't like how the CI build behaves.

	Then visit one of ~~the~~ links above and find a workflow run item for your platform. Workflow items are the things in the list. The tags are flagged as <code>CI (Windows)</code>, <code>CI (Linux)</code>, or <code>CI (macOS)</code> in the second row of each workflow item in the list (not the filter in the left hand nav menu). Click on a completed workfow item (only items with green checkmarks will have created downloadable binaries yet), find the Artifacts section at the bottom (note again: you need to be signed up to see that section and/or download the artifact), then click the Download button. Unzip the downloaded file and find the main binary (with the same name as above). Copy the main binary to the install location, overwriting the original one, and run MAME the same way you were running it before. On Windows and macOS, you need to repeat the security steps above to trust the new MAME executable.		Then visit one of your preferred "Actions page" links above and find a workflow run item for your platform. Workflow items are the things in the list. The tags are flagged as <code>CI (Windows)</code>, <code>CI (Linux)</code>, or <code>CI (macOS)</code> in the second row of each workflow item in the list (not the filter in the left hand nav menu). Click on a ''completed workfow item'' (only items with green checkmarks will have created downloadable binaries yet), find the Artifacts section at the bottom (note again: ''you need to be signed up to see that section and/or download the artifact''), then click the Download button. Unzip the downloaded file and find the main binary (with the same name as above). Copy the main binary to the install location, overwriting the original one, and run MAME the same way you were running it before. On Windows and macOS, you need to repeat the security steps above to trust the new MAME executable.

	= More MAME related links =		= More MAME related links =

Johnnyo: /* Continuous Integration MAME Builds */ improving? links

2026-06-02T20:30:58Z

Continuous Integration MAME Builds: improving? links

← Older revision		Revision as of 21:30, 2 June 2026
Line 164:		Line 164:
	Continuous Integration (CI) builds are available from both :		Continuous Integration (CI) builds are available from both :

	* the [https://github.com/mamedev/mame/actions https://github.com/mamedev/mame/actions primary MAME repo Actions pagee] and		* the [https://github.com/mamedev/mame/actions https://github.com/mamedev/mame/actions -- primary MAME repo Actions pagee] and

	* [https://github.com/holub/mame/actions https://github.com/holub/mame/actions Holub's GitHub repo Actions page].		* [https://github.com/holub/mame/actions https://github.com/holub/mame/actions -- Holub's GitHub repo Actions page].

	Both are newer builds than the latest official release, and Holub's repo still tends to contain the fixes still waiting to be accepted to the primary repo. MAME CI builds are available for Windows, Linux, and macOS and are updated automatically whenever code is committed by a maintainer or pushed to the primary repo.		Both are newer builds than the latest official release, and Holub's repo still tends to contain the fixes still waiting to be accepted to the primary repo. MAME CI builds are available for Windows, Linux, and macOS and are updated automatically whenever code is committed by a maintainer or pushed to the primary repo.

Johnnyo: /* Continuous Integration MAME Builds */ official

2026-06-02T20:16:35Z

Continuous Integration MAME Builds: official

← Older revision		Revision as of 21:16, 2 June 2026
Line 168:		Line 168:
	* [https://github.com/holub/mame/actions https://github.com/holub/mame/actions Holub's GitHub repo Actions page].		* [https://github.com/holub/mame/actions https://github.com/holub/mame/actions Holub's GitHub repo Actions page].

	Both are newer builds than the latest release, and Holub's repo still tends to contain the fixes still waiting to be accepted to the primary repo. MAME CI builds are available for Windows, Linux, and macOS and are updated automatically whenever code is committed by a maintainer or pushed to the primary repo.		Both are newer builds than the latest official release, and Holub's repo still tends to contain the fixes still waiting to be accepted to the primary repo. MAME CI builds are available for Windows, Linux, and macOS and are updated automatically whenever code is committed by a maintainer or pushed to the primary repo.

	'''You need to be logged in to github''' to download CI artifacts, so [https://github.com/login sign in] or [https://github.com/signup sign up].		'''You need to be logged in to github''' to download CI artifacts, so [https://github.com/login sign in] or [https://github.com/signup sign up].

Johnnyo: /* Continuous Integration MAME Builds */ actions pages more prominent

2026-06-02T20:14:58Z

Continuous Integration MAME Builds: actions pages more prominent

← Older revision		Revision as of 21:14, 2 June 2026
Line 162:		Line 162:
	MAME is updated on a release schedule, but due to the ongoing nature of development, including for the MAME Next machine, it can sometimes be useful to install a more recent build if it contains a new feature or bugfix you are interested in. Sometimes, this ongoing work is discussed on social media, such as the [https://discordapp.com/channels/556228195767156758/752197165891321886 Next Developer Discord].		MAME is updated on a release schedule, but due to the ongoing nature of development, including for the MAME Next machine, it can sometimes be useful to install a more recent build if it contains a new feature or bugfix you are interested in. Sometimes, this ongoing work is discussed on social media, such as the [https://discordapp.com/channels/556228195767156758/752197165891321886 Next Developer Discord].

	Continuous Integration (CI) builds are available from both the [https://github.com/mamedev/mame/actions primary MAME repo] and [https://github.com/holub/mame/actions holub's GitHub repo]. Both are ~~considered bleeding-edge~~, ~~with~~ the primary ~~MAME~~ repo ~~slightly less so~~. MAME CI builds are available for Windows, Linux, and macOS and are updated automatically whenever code is committed by a maintainer or pushed to the primary repo.		Continuous Integration (CI) builds are available from both :

			* the [https://github.com/mamedev/mame/actions https://github.com/mamedev/mame/actions primary MAME repo Actions pagee] and

			* [https://github.com/holub/mame/actions https://github.com/holub/mame/actions Holub's GitHub repo Actions page].

			Both are newer builds than the latest release, and Holub's repo still tends to contain the fixes still waiting to be accepted to the primary repo. MAME CI builds are available for Windows, Linux, and macOS and are updated automatically whenever code is committed by a maintainer or pushed to the primary repo.

	'''You need to be logged in to github''' to download CI artifacts, so [https://github.com/login sign in] or [https://github.com/signup sign up].		'''You need to be logged in to github''' to download CI artifacts, so [https://github.com/login sign in] or [https://github.com/signup sign up].

Johnnyo: core 3.02.04

2026-06-01T23:13:53Z

core 3.02.04

← Older revision		Revision as of 00:13, 2 June 2026
Line 1:		Line 1:
	[https://www.mamedev.org/ MAME] (formerly an acronym of Multiple Arcade Machine Emulator) is a free and open-source emulator designed to emulate the hardware of arcade games, later expanded to include video game consoles, old computers and other systems in software on modern personal computers and other platforms.		[https://www.mamedev.org/ MAME] (formerly an acronym of Multiple Arcade Machine Emulator) is a free and open-source emulator designed to emulate the hardware of arcade games, later expanded to include video game consoles, old computers and other systems in software on modern personal computers and other platforms.

	MAME has supported the ZX Spectrum Next since version 0.267. The existing implementation is based on the v3.02.01 core and implements most of the features.		MAME has supported the ZX Spectrum Next since version 0.267. The existing implementation is based on the v3.02.04 core and implements most of the features.

	= Installation =		= Installation =

Orcmeal: Added info about required SDL3 library when installing on macOS.

2026-05-12T16:24:05Z

Added info about required SDL3 library when installing on macOS.

← Older revision		Revision as of 17:24, 12 May 2026
Line 13:		Line 13:

	* '''Windows:''' Download [https://www.mamedev.org/release.html MAME for Windows].		* '''Windows:''' Download [https://www.mamedev.org/release.html MAME for Windows].
	* '''macOS:''' Download [https://sdlmame.lngn.net/ MAME for macOS].		* '''macOS:''' Download the [https://github.com/libsdl-org/SDL/releases/latest SDL3 library], and copy its '''SDL3.xcframework''' and '''share''' folders to ~/Library/Frameworks, as instructed in the included INSTALL.md file. Then download [https://sdlmame.lngn.net/ MAME for macOS].
	* '''Linux:''' Install MAME from the flatpak repositories by running:		* '''Linux:''' Install MAME from the flatpak repositories by running:
	<pre>sudo flatpak install org.mamedev.MAME</pre>		<pre>sudo flatpak install org.mamedev.MAME</pre>

	Note that Windows and macOS will likely prevent you from launching MAME directly for security reasons. See below on how to solve this.		Note that Windows and macOS will likely prevent you from launching MAME (and the SDL3 framework) directly for security reasons. See below on how to solve this.

	Alternatively, for the MAME platform as a whole, you can also check your package manager, or [https://docs.mamedev.org/initialsetup/compilingmame.html build from sources].		Alternatively, for the MAME platform as a whole, you can also check your package manager, or [https://docs.mamedev.org/initialsetup/compilingmame.html build from sources].
Line 93:		Line 93:
	Now launch MAME again. A dialog will ask once more if you want to open “mame”. Click “Open Anyway”, and enter your password or use Touch ID when prompted by macOS.		Now launch MAME again. A dialog will ask once more if you want to open “mame”. Click “Open Anyway”, and enter your password or use Touch ID when prompted by macOS.

	From now on, you can launch this version of MAME without warnings. However, you '''will''' need to repeat this each time you update MAME.		You will then need to '''repeat this process for the SDL3 framework.'''

			From now on, you can launch this version of MAME without warnings. However, you '''will''' need to repeat this each time you update MAME or the SDL3 framework.

	= Keys =		= Keys =

Orcmeal at 16:17, 12 May 2026

2026-05-12T16:17:19Z

← Older revision		Revision as of 17:17, 12 May 2026
Line 9:		Line 9:
	=== 1. Get MAME ===		=== 1. Get MAME ===
	Start with these official MAME releases. If you encounter crashes or other bugs, try replacing the MAME executable with holub's latest Continuous Integration (CI) builds as described at the end of this article.		Start with these official MAME releases. If you encounter crashes or other bugs, try replacing the MAME executable with holub's latest Continuous Integration (CI) builds as described at the end of this article.

			MAME for macOS now requires the SDL3 library.

	* '''Windows:''' Download [https://www.mamedev.org/release.html MAME for Windows].		* '''Windows:''' Download [https://www.mamedev.org/release.html MAME for Windows].