Difference between revisions of "Emulator:MESS"

From Wah!ki
Jump to navigation Jump to search
Line 1: Line 1:
 
== About ==
 
== About ==
 +
MESS stands for Multi Emulator Super System, the goal of the project was simlar to MAME where MAME only emulated arcade systems MESS took the MAME source code and extended it to include support for consoles, computer systems and calculators. That is not to say the scope was limited to only these 3 classes of device, The MESS project was happy to emulate  any non-arcade system, leaving the arcade work up to the MAME project.
 +
 +
Being based on the same source code oas the MAME project means the project shared similar goals, that is accuracy and documentation over playability with the byproduct of accurate emulation being the ability to load ROMs.
 +
 +
'''As of MAME 0.167''' the MESS source code was integrated into the main MAME source tree and the projects unified. This made sense because of the lot of the contributors to MESS were also MAME developers and the projects shared a common codebase.
 +
 +
The default MAME compilation as of 0.167 will build a unified MAME/MESS project (commonly referred to as UME) although as of MAME 0.217 it is still possible to build MESS alone by passing a SUBPROJECT variable during compilation.
 +
 +
 
[http://www.mess.org/ Project Homepage]
 
[http://www.mess.org/ Project Homepage]
  

Revision as of 05:17, 25 January 2020

About

MESS stands for Multi Emulator Super System, the goal of the project was simlar to MAME where MAME only emulated arcade systems MESS took the MAME source code and extended it to include support for consoles, computer systems and calculators. That is not to say the scope was limited to only these 3 classes of device, The MESS project was happy to emulate any non-arcade system, leaving the arcade work up to the MAME project.

Being based on the same source code oas the MAME project means the project shared similar goals, that is accuracy and documentation over playability with the byproduct of accurate emulation being the ability to load ROMs.

As of MAME 0.167 the MESS source code was integrated into the main MAME source tree and the projects unified. This made sense because of the lot of the contributors to MESS were also MAME developers and the projects shared a common codebase.

The default MAME compilation as of 0.167 will build a unified MAME/MESS project (commonly referred to as UME) although as of MAME 0.217 it is still possible to build MESS alone by passing a SUBPROJECT variable during compilation.


Project Homepage

Configuration

Platform Version Device Exec Type commandline_format
Linux 000000 N/A README D N.A