I completely reworked these unmaintained ports. I turned mess into a
proper slave port as the differences from mame were few. Some notes:
* converted to GitHub (this saved messing with the double-zip /
dos2unix per file arrangement, no more post-extract target)
* got rid of patchlevel support accordingly
* got rid of DIST_SUBDIR accordingly
* Clang from FreeBSD 10 cannot build this! It fails will some kind of
signal. I did not test on FreeBSD 11 yet. For now, degrade the
ports to use GCC always. Note the makefiles were hardcoded to GCC.
I fixed the hardcoding so it uses environment but perhaps it's known
that mame/mess is now gcc-only
* Some options are no longer optional, e.g. BUILTIN_DEBUGGER, SDL2
These were made unconditional accordingly.
* mess is now a minimal slave port. There are some additions to mame
Makefile to support the slave.
* I used PORTDOCS and PORTEXAMPLE to simplify each pkg-plist
* DragonFly support still pending. This port discovered a bug in
GCC 5.1 release which has been fixed recently, so the base compiler
has to be upgraded before testing can resume.
- Reflow pkg-descr and add trailing slash to URL [1]
- Trim Makefile headers [1]
- Fix improper overwriting of FILE make variable [1]
- Works fine with clang, so don't depend on gcc 4.6+ where clang
is available (taken from libreoffice port)
PR: ports/171994 [1]
Submitted by: KATO Tsuguru <tkato432@yahoo.com>
Feature safe: yes
- Mirror to my FTP since it can't be downloaded by fetch [1].
- Remove BROKEN.
PR: ports/117903
Submitted by: "Pedro F. Giffuni" <giffunip@tutopia.com>
Reworked by: alepulver (myself) [1]
Approved by: portmgr (linimon)
- The wrapper script additional output has been removed so programs that parse
the output do not get unexpected data.
Submitted by: nikow <madleser@gmx.de> (private e-mail)
it's development:
1) Run on Linux/Unix, Mac OS X, and other SDL supported operating systems with
as few changes as possible to the base Win32 code. This means we can track
changes faster than larger more conventional ports such as MacMAME, and we
also maintain what I call "Firefox compatibilty" where learning a major app
only needs to be done once per application, and it then applies across many
operating systems. If you can use the command-line Win32 MAME, you already
know how to use SDLMAME on any platform you may encounter it on.
2) MAME developers are important. By keeping quickly up to date, we make it
easy for people on non-Windows platforms to make and submit changes to the
core MAME code, and we offer native implementations of MAME's multi-window
GUI debugger on both Linux/Unix and Mac OS X.
WWW: http://rbelmont.mameworld.info/?page_id=163
