Ability to compile mame

[don999]

I was fiddling around with Debian 9.3 and thought, what if I installed Debian 9.3 i386 32 bit on an external usb hard drive and see if I could compile mame 194.

I was able to compile mame 194 myself after removing a few items from the compile specifically the barcrest and bfm games, otherwise it would exhaust the virtual memory with gcc v6.3.0.



This comments out the barcrest and bfm in mame.lst with c style comments: Adding 6 lines.

diff ../mame194orig/src/mame/mame.lst  src/mame/mame.lst 
2875a2876
> /*
8683a8685
> */
21424a21427
> /*
27842a27846
> */
32555a32560
> /*
32558a32564
> */

diff ../mame194orig/src/mame/mame.lst  src/mame/mame.lst -u5
--- ../mame194orig/src/mame/mame.lst    2018-01-31 11:19:22.000000000 -0500
+++ src/mame/mame.lst    2018-03-12 04:39:47.748825373 -0400
@@ -2871,10 +2871,11 @@
 bestleaw                        // bootleg
 
 @source:beta.cpp
 beta                            //
 
+/*
 @source:bfcobra.cpp
 beeline                         // 1991 BFM
 escounts                        // 1990 BFM
 inquiztr                        // 1989 BFM
 qos                             // 1992 BFM
@@ -8679,10 +8680,11 @@
 b85ritzc                        //
 b85ritzd                        //
 b85royal                        //
 b85scard                        // (c) 198? BFM
 b85sngam                        //
+*/
 
 @source:bgt.cpp
 bg_barmy                        //
 bg_ddb                          //
 bg_max                          //
@@ -21420,10 +21422,11 @@
 mps1230                         // 1988 Commodore MPS-1230 near-letter-quality dot matrix printer
 
 @source:mpu12wbk.cpp
 fruitstb                        //
 
+/*
 @source:mpu2.cpp
 m2hilite                        // Hi-Lights (Barcrest) (MPU2)
 m2svlite                        // Silver Lights (Barcrest) (MPU2)
 
 @source:mpu3.cpp
@@ -27838,10 +27841,11 @@
 m5xfact                         // X Factor (Empire)
 m5xfact02                       //
 m5xfact04                       //
 m5xfact11                       //
 m5zigzag                        // Zig Zag
+*/
 
 @source:mpz80.cpp
 mpz80                           //
 
 @source:mquake.cpp
@@ -32551,13 +32555,15 @@
 rastanub                        // B04 (c) 1987 Taito America Corporation (US)
 rastsaga                        // B04 (c) 1987 Taito Corporation (Japan)
 rastsagaa                       // B04 (c) 1987 Taito Corporation (Japan)
 rastsagab                       // B04 (c) 1987 Taito Corporation (Japan)
 
+/*
 @source:rastersp.cpp
 fbcrazy                         // 1997
 rotr                            // 1994
+*/
 
 @source:ravens.cpp
 ravens                          //
 ravens2                         //

This comments out barcrest and bfm using lua style comments. Changing 6 lines.

diff ../mame194orig/scripts/target/mame/arcade.lua scripts/target/mame/arcade.lua 
747,748c747,748
<         "barcrest",
<         "bfm",
---
>     --    "barcrest",
>     --    "bfm",
1283a1284
> --[[
1308a1310,1311
> --]]
> --[[
1340a1344
> --]]


diff ../mame194orig/scripts/target/mame/arcade.lua scripts/target/mame/arcade.lua -u5
--- ../mame194orig/scripts/target/mame/arcade.lua    2018-01-31 11:18:24.000000000 -0500
+++ scripts/target/mame/arcade.lua    2018-03-11 14:05:01.899315814 -0400
@@ -742,12 +742,12 @@
         "amiga",
         "aristocr",
         "ascii",
         "atari",
         "atlus",
-        "barcrest",
-        "bfm",
+    --    "barcrest",
+    --    "bfm",
         "bmc",
         "capcom",
         "ces",
         "cinemat",
         "comad",
@@ -1279,10 +1279,11 @@
     MAME_DIR .. "src/mame/includes/powerins.h",
     MAME_DIR .. "src/mame/video/powerins.cpp",
     MAME_DIR .. "src/mame/drivers/bowltry.cpp",
 }
 
+--[[
 createMAMEProjects(_target, _subtarget, "barcrest")
 files {
     MAME_DIR .. "src/mame/drivers/mpu2.cpp",
     MAME_DIR .. "src/mame/drivers/mpu3.cpp",
     MAME_DIR .. "src/mame/machine/mpu4.cpp",
@@ -1304,10 +1305,12 @@
     MAME_DIR .. "src/mame/drivers/mpu4vid.cpp",
     MAME_DIR .. "src/mame/drivers/mpu5.cpp",
     MAME_DIR .. "src/mame/drivers/mpu5.hxx",
 }
 
+--]]
+--[[
 createMAMEProjects(_target, _subtarget, "bfm")
 files {
     MAME_DIR .. "src/mame/drivers/bfcobra.cpp",
     MAME_DIR .. "src/mame/machine/bfm_comn.cpp",
     MAME_DIR .. "src/mame/machine/bfm_comn.h",
@@ -1336,10 +1339,11 @@
     MAME_DIR .. "src/mame/machine/bfm_bda.h",
     MAME_DIR .. "src/mame/video/bfm_dm01.cpp",
     MAME_DIR .. "src/mame/video/bfm_dm01.h",
     MAME_DIR .. "src/mame/drivers/rastersp.cpp",
 }
+--]]
 
 createMAMEProjects(_target, _subtarget, "bmc")
 files {
     MAME_DIR .. "src/mame/drivers/bmcbowl.cpp",
     MAME_DIR .. "src/mame/drivers/koftball.cpp",

To my surprise, the compiled binary worked perfectly on knoppix 8.1. I guess it's not too surprising considering they are both based on debian.9.3.

lsb_release -a
No LSB modules are available.
Distributor ID:    Debian
Description:    Debian GNU/Linux 9.3 (stretch)
Release:    9.3
Codename:    stretch

./mame  -sdlvideofps galaxian -verbose -video opengl
Available videodrivers: x11 wayland dummy 
Current Videodriver: x11
    Display #0
        Renderdrivers:
                opengl (0x0)
             opengles2 (0x0)
              software (0x0)
Available audio drivers: 
    pulseaudio          
    alsa                
    sndio               
    dsp                 
    disk                
    dummy               
Build version:      0.194 (unknown)
Build architecure:  
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1 
Build defines 1:    LSB_FIRST=1 
SDL/OpenGL defines: SDL_COMPILEDVERSION=2005 USE_OPENGL=1 
Compiler defines A: __GNUC__=6 __GNUC_MINOR__=3 __GNUC_PATCHLEVEL__=0 __VERSION__="6.3.0 20170516" 
Compiler defines B: __unix__=1 __i386__=1 
Compiler defines C: __USE_FORTIFY_LEVEL=0 
Enter init_monitors
Adding monitor screen0 (1920 x 1080)
Leave init_monitors
Enter sdlwindow_init
Using SDL multi-window OpenGL driver (SDL 2.0+)
...snip...
GL texture: copy 0, shader 0, dynamic 0, 768x224 768x224 [RGB32, Equal: 1, Palette: 0,
            scale 1x1, border 0, pitch 1152,768/2048], bytes/pix 4
GL texture: copy 0, shader 0, dynamic 0, 768x224 768x224 [RGB32, Equal: 1, Palette: 0,
            scale 1x1, border 0, pitch 1152,768/2048], bytes/pix 4
  0.02s,    1 F, avrg game: 60.24 FPS 16.60 ms/f, avrg video: 731.20 FPS 1.37 ms/f, last video:   inf FPS 0.73 ms/f
  1.02s,   62 F, avrg game: 60.61 FPS 16.50 ms/f, avrg video: 1288.61 FPS 0.78 ms/f, last video:   inf FPS 0.66 ms/f
  2.03s,  123 F, avrg game: 60.60 FPS 16.50 ms/f, avrg video: 1356.92 FPS 0.74 ms/f, last video:   inf FPS 0.69 ms/f
  3.04s,  184 F, avrg game: 60.60 FPS 16.50 ms/f, avrg video: 1312.29 FPS 0.76 ms/f, last video:   inf FPS 0.81 ms/f
Average speed: 100.00% (4 seconds)
sdl_kill: closing audio
Sound buffer: overflows=3 underflows=0
Enter sdlwindow_exit
Leave sdlwindow_exit

So while it's not compiling under knoppix 8.1 itself, it's the next best thing.

[don999]

=========================

Knoppix 9.1 and mame

==========================


I wanted to see if I could get knoppix9.1 working with mame,

"lsb_release -a"
says that it's running "bullseye/sid"

so I went to packages.debian.org and looked under bullseye and found

https://packages.debian.org/bullseye/i386/games/mame
https://packages.debian.org/bullseye...ames/mame-data
https://packages.debian.org/bullseye...games/mame-doc
https://packages.debian.org/bullseye/i386/liblua5.3-0
https://packages.debian.org/bullseye/i386/libpugixml1v5


and get all of these and make sure that you get the "i386" version

then you should have these files:

mame_0.228+dfsg.1-1_i386.deb
mame-data_0.228+dfsg.1-1_all.deb  
mame-doc_0.228+dfsg.1-1_all.deb 

liblua5.3-0_5.3.3-1.1+b1_i386.deb  
libpugixml1v5_1.11.4-1_i386.deb

and then use dpkg -i to install them:

sudo dpkg -i  libpugixml1v5_1.11.4-1_i386.deb  mame-data_0.228+dfsg.1-1_all.deb mame-doc_0.228+dfsg.1-1_all.deb liblua5.3-0_5.3.3-1.1+b1_i386.deb mame_0.228+dfsg.1-1_i386.deb

That should install all of the mame stuff.

set $roms to where you've got your roms. For example, say I've got my roms in two different directories:

ROMS="/media/sdb1/roms;/media/sdb1/soft"

then launch mame with

mame -rompath "$ROMS"

=====================================


I had a little bit of trouble getting the joystick (mame uses SDL2 for joystick input) to work under sdl2 because of permissions, you may try a couple of things:

I installed evtest as well from:

https://packages.debian.org/bullseye/i386/utils/evtest

so if you run "sudo evtest" it will give you a list. Figure out which one is your joystick, and then

If you don't want to install evtest, you could try just looking at /proc/bus/input/devices:

cat /proc/bus/input/devices

ls -l /dev/input
drwxr-xr-x 2 root root     220 Sep 27 14:28 by-id
drwxr-xr-x 2 root root     240 Sep 27 14:28 by-path
crw-rw---- 1 root input 13, 64 Aug  7 08:56 event0
crw-rw---- 1 root input 13, 65 Aug  7 08:56 event1
crw-rw---- 1 root input 13, 76 Aug  7 08:56 event12
crw-rw---- 1 root input 13, 77 Aug  7 08:56 event13
crw-rw---- 1 root input 13, 78 Aug  7 08:56 event14
crw-rw---- 1 root input 13, 79 Aug  7 08:56 event15
crw-rw---- 1 root input 13, 80 Aug  7 08:56 event16
crw-rw---- 1 root input 13, 81 Aug  7 08:56 event17
crw-rw---- 1 root input 13, 82 Aug  7 08:56 event18
crw-rw---- 1 root input 13, 83 Aug  7 08:56 event19
crw-rw---- 1 root input 13, 66 Aug  7 08:56 event2
crw-rw---- 1 root input 13, 67 Sep 27 14:28 event3
crw-rw---- 1 root input 13, 68 Sep 27 14:28 event4
crw-rw---- 1 root input 13, 69 Aug  7 08:56 event5
crw-rw---- 1 root input 13, 70 Aug  7 08:56 event6
crw-rw---- 1 root input 13, 71 Sep 27 14:28 event7
crw-rw---- 1 root input 13, 72 Sep 27 14:28 event8
crw-rw---- 1 root input 13, 73 Sep 27 14:28 event9
crw-rw-r-- 1 root input 13,  1 Aug  7 08:56 js1
crw-rw---- 1 root input 13, 63 Aug  7 08:56 mice
crw-rw---- 1 root input 13, 32 Aug  7 08:56 mouse0
crw-rw---- 1 root input 13, 33 Aug  7 08:56 mouse1
crw-rw---- 1 root input 13, 34 Aug  7 08:56 mouse2
crw-rw---- 1 root input 13, 35 Sep 27 14:28 mouse3

Notice how js1 has the crw-rw-r--? SDL2 doesn't use the /dev/input/jsX, but rather one of the /dev/input/eventXX, and I think it has to have the a+r set.

"sudo chmod a+r /dev/input/event22"

if the list says your joystick is event 22
This will open up the permissions for /dev/input/event22 so "all can read" it.

so if you launch mame with -verbose it should show your joystick getting opened.

Some discussion about the issue here:
https://discourse.libsdl.org/t/sdl2-requires-root-privileges-to-use-joysticks-in-linux/20181

https://stackoverflow.com/questions/...ck-but-os-does

another thing you could try is to add the user "knoppix" to the "input" group.

groups knoppix  (will show the groups that knoppix is part of)
sudo adduser knoppix input

[don999]

=========================

Knoppix 9.1 and mame 235

==========================

You can install mame 235 and run under knoppix9.1 by getting the debian i386 packages from testing (bookworm):


https://packages.debian.org/bookworm/i386/mame/download

Download Page for mame_0.235+dfsg.1-2_i386.deb

https://packages.debian.org/bookworm...-data/download

Download Page for mame-data_0.235+dfsg.1-2_all.deb


You still need these files also (see my previous post about mame 228 above for more information)

liblua5.3-0_5.3.3-1.1+b1_i386.deb
libpugixml1v5_1.11.4-1_i386.deb

You can also get mame-doc (0.235+dfsg.1-2) if you like.

Then just put them all in a directory and "sudo dpkg -i *.deb" and then you should be able to run mame 235 by running "mame".

Mame 235 is only a couple of months old, so it's pretty up to date.

=======================

(The Mame 237 debs in sid won't work on knoppix 9.1)

If you search at package.debian.org for mame there's various versions available, 235 being the most recent that will work on knoppix 9.1.


stretch (oldoldstable) (games): Multiple Arcade Machine Emulator (MAME)
0.182-1: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x
buster (oldstable) (games): Multiple Arcade Machine Emulator (MAME)
0.206+dfsg.1-1: amd64 arm64 armel armhf i386 mips mips64el mipsel s390x
bullseye (stable) (games): Multiple Arcade Machine Emulator (MAME)
0.228+dfsg.1-1: amd64 arm64 armhf i386 mips64el ppc64el s390x
bookworm (testing) (games): Multiple Arcade Machine Emulator (MAME)
0.235+dfsg.1-2: amd64 arm64 armel armhf i386 mips64el ppc64el s390x
sid (unstable) (games): Multiple Arcade Machine Emulator (MAME)
0.237+dfsg.1-1: amd64 arm64 armel armhf hppa i386 mips64el mipsel ppc64 ppc64el riscv64 s390x sh4 sparc64 x32

[don999]

=========================

Knoppix 9.1 and other emulators

==========================
You can get other emulators running also, not just mame. I was able to get:

atari800
vice (name of executable program is x64, xpet, x128 )
dosbox
fs-uae
stella

running on knoppix9.1 by downloading the deb packages from package.debian.com (bullseye stable)

You could also use synaptic to download the packages, but I like the debs so I can install it offline (no internet necessary).


atari800_4.1.0-3_i386.deb
vice_3.5.0.dfsg-3_i386.deb (c64 emulator)
stella_6.5.2-1_i386.deb (atari 2600 emulator)

dosbox_0.74-3-3_i386.deb (dos games emulator)
libsdl-sound1.2_1.0.3-9+b1_i386.deb

fs-uae_3.0.5+dfsg-1_i386.deb (fs-uae is an amiga emulator)
fs-uae-launcher_3.0.5+dfsg-1_all.deb
python3-pyqt5.qtopengl_5.15.2+dfsg-3_i386.deb

There's other emulators too:
https://packages.debian.org/bullseye/games-emulator

(This metapackage lists a bunch of emulator packages)

[don999]

=========================

Getting the joystick/gamepad working (using setfacl)

==========================

Okay, I have spent way more time than I ever wanted to fiddling with permissions and the like. However, I've found a pretty simple way to get the joystick working.

There's actually two different styles of joystick access: one is with /dev/input/eventX and the other is with /dev/input/jsX.

I think /dev/input/eventX is the more recent, and /dev/input/jsX is the "old" way.

So when I boot knoppix, my gamepad shows up as /dev/input/event4. So you'll need to figure out which file represents your gamepad.

When I do a "ls -l /dev/input/by-id" the gamepad has a symlink to /dev/input/event4.

So I do this:

sudo setfacl -m "u:knoppix:rw-" /dev/input/event4
sudo setfacl -m "u:knoppix:rw-" /dev/input/js0
touch /dev/input/js0

so once you "touch" the js0, it sets up a symlink to /dev/input/js0 in the /dev/input/by-id directory.
When you run touch, it may complain about not being able to set the time. (Doesn't seem to hurt anything)
The reason I use "touch" is to make an access to /dev/input/js0.
Running "hexdump -C /dev/input/js0" would do the same thing (CTRL+C to exit after generating some joystick activity).

The setfacl commands above will give the user knoppix read and write file access using an access control list. setfacl = set file access control list (-m is modify).
getfacl = get file access control list.
If you do a "ls -l /dev/input" you will see a + after rw-rw-r--+, the + indicates that there's an access control list for that file.

So as a test, launch chromium or firefox, go to "about:blank" and bring up the f12 console. Press a joystick button. Type "navigator:getGamepads()" and hit enter.
Remember that you have to generate joystick activity (like pressing buttons) to see the gamepad in chromium or firefox.

If your joystick is working on /dev/input/js0 you should see a list like

(firefox) 
navigator.getGamepads() 

Array [ Gamepad ]

(chromium) 
navigator.getGamepads()
GamepadList {0: Gamepad, 1: null, 2: null, 3: null, length: 4}

If it isn't working, you will see

(firefox)
navigator.getGamepads() 

Array []

(chromium)
navigator.getGamepads()
GamepadList {0: null, 1: null, 2: null, 3: null, length: 4}

Once you enter the commands below, press a joystick button. Type "navigator:getGamepads()" and hit enter. You don't have to relaunch firefox or chromium if it's already open, it should work.

echo launch chromium or firefox here and getGamepads here wont work
sudo setfacl -m "u:knoppix:rw-" /dev/input/event4
sudo setfacl -m "u:knoppix:rw-" /dev/input/js0
touch /dev/input/js0
echo now getGamepads here should work

[don999]

============================
Being able to compile mame 238 in knoppix 9.1
============================

What's necessary to compile mame is just:

sudo apt-get install git build-essential python libsdl2-dev libsdl2-ttf-dev libfontconfig-dev libpulse-dev qt5-default

but what if we wanted to be able to compile mame by adding .deb packages manually?

I got the following packages from packages.debian.org:

libasound2-dev_1.2.4-1.1_i386.deb
libpulse-dev_14.2-2_i386.deb
libqt5core5a_5.15.2+dfsg-9_i386.deb
libqt5gui5_5.15.2+dfsg-9_i386.deb
libqt5widgets5_5.15.2+dfsg-9_i386.deb
libsdl2-dev_2.0.14+dfsg2-3_i386.deb
libsdl2-ttf-dev_2.0.15+dfsg1-1_i386.deb
libsdl-sound1.2_1.0.3-9+b1_i386.deb
libsndio-dev_1.5.0-3_i386.deb
libudev-dev_247.3-6_i386.deb
qtbase5-dev_5.15.2+dfsg-9_i386.deb
qtbase5-dev-tools_5.15.2+dfsg-9_i386.deb

also need these to run:

liblua5.3-0_5.3.3-1.1+b1_i386.deb
libpugixml1v5_1.11.4-1_i386.deb

So put them all in a directory then:

sudo dpkg -i --force-depends *.deb

and it will install them all at once. We use --force-depends because we haven't actually got every package needed to satisfy all the dependencies.


Get the source for mame0238 and extracting the mame0238.exe, cd into the directory, edit the makefile with
"nano makefile" so that we specify our compile to be 32 bit and where to find qt5:


#PTR64 = 1
edit to say
PTR64 = 0
since we're compiling for an 32 bit target

and also

#QT_HOME = /usr/lib/qt5/
edit to
QT_HOME = /usr/lib/i386-linux-gnu/qt5/

then save it with CTRL+O, exit with CTRL+X.

time make -j4

and it should be able to complete the compile.

and launch your freshly compiled mame with

./mame -rompath "path_to_my_roms"

[don999]

The last version of mame that is compileable under knoppix 9.1 is mame 264. 265 and above require a more up to date compiler.