Unofficial, fully static AppImage of MAME's chdman (Compressed Hunks of
Data manager) for x86_64 Linux. Static means no glibc or library requirements
whatsoever — it runs on any distribution, however old or new, including
minimal containers and distros without FUSE.
Built automatically from the latest MAME
release every week. Companion repo:
unecm-appimage (decodes .ecm
files — chdman cannot read them).
am -e https://github.com/hcet-sudo/chdman-appimage chdman chdman
curl -LO https://github.com/hcet-sudo/chdman-appimage/releases/latest/download/chdman-x86_64.AppImage
chmod +x chdman-x86_64.AppImage
Without FUSE, run ./chdman-x86_64.AppImage --appimage-extract-and-run ....
./chdman-x86_64.AppImage createcd -i game.cue -o game.chd # CD image -> CHD
./chdman-x86_64.AppImage createdvd -i game.iso -o game.chd # DVD image -> CHD
./chdman-x86_64.AppImage extractcd -i game.chd -o out.cue # CHD -> cue/bin
./chdman-x86_64.AppImage verify -i game.chd
./chdman-x86_64.AppImage info -i game.chd
Have a .bin.ecm? That is ECM format, not CHD — decode it first with
unecm, then use the cue sheet
above (a minimal one for MODE1/2352 images):
FILE "game.bin" BINARY
TRACK 01 MODE1/2352
INDEX 01 00:00:00
The GitHub Actions workflow (.github/workflows/release.yml) runs every
Monday and on demand, then:
- Resolves the latest MAME release tag via the GitHub API.
- Builds
chdmanstatically from that tag's source. - Self-tests it — generates a valid MODE1/2352 CD image, converts it
with
createcd, extracts it back withextractcd, and requires bit-identical results, plusverifyandinfoon the CHD. - ISA-gates it — the release only publishes if the same bit-perfect
self-test also passes under
qemuemulating a baseline x86-64-v1 CPU. Any v2+ instruction (from our code or from prebuilt static glibc) dies with SIGILL there and blocks the release — so the AppImage runs on every x86_64 CPU, however old. - Publishes a release tagged
<ver>@<date>_<epoch>(e.g.0.289@2026-11-17_1763...) with the stable asset namechdman-x86_64.AppImage, soreleases/latest/download/...always points at the newest build.
Manual runs: Actions → Build and release → Run workflow (optionally pin a
MAME tag, e.g. mame0289). Pushes that touch build/ or the workflow also
rebuild.
sudo apt-get install -y gcc g++ make python3 libsdl2-dev libfontconfig1-dev
bash build/build-chdman.sh mame0289 # downloads + compiles MAME tools
bash build/self-test-chdman.sh dist/chdman-x86_64.AppImage
The recipe builds only the tools (EMULATOR=0, no Qt debugger, no MIDI, no
bgfx) and links them statically (LDOPTS="-static", plus no-op SDL clipboard
stubs — see build/build-chdman.sh), so the result has zero runtime
dependencies.
- Replace
hcet-sudowith your GitHub username in this README:grep -rl hcet-sudo . | xargs sed -i 's/hcet-sudo/yourname/g'. - Push the repo to GitHub (terminal or the web UI's "Upload files" flow —
the workflows invoke scripts via
bash, so missing execute bits on web-uploaded files don't matter). - Repo Settings → Actions → General → Workflow permissions → Read and write (the release job needs write access to publish releases).
- Test with Actions → "Build and release" → Run workflow; the weekly cron then tracks new MAME releases automatically.
To make plain am -i chdman work for everyone, submit an installation
script to the AM database: run
am -t chdman, choose the GitHub option, then open a PR adding the
generated script to programs/x86_64/ and its name to the x86_64-apps
list. (As of Nov 2026 there is no chdman entry in the AM database — you
would be the first.)
- MAME and
chdmanare distributed under the GNU GPL v2 or later (LICENSE-MAMEis MAME'sCOPYINGverbatim). MAME is a registered trademark of Gregory Ember. - Build scripts and icons in this repo: GPL-2.0-or-later, same license.
- This is an unofficial build; file MAME bugs upstream at mamedev/mame, and build issues here.