mirror of
https://github.com/Abdess/retroarch_system.git
synced 2026-11-11 12:33:53 -06:00
Abdessamad Derraz
ab9fe76de2
ArkOS ran the GBA with gpsp_ezode_mod and dArkOS with mgba_rumble: no profile named them, so an install for the card's games kept every GBA core's files, FBNeo's 3,472 data files among them. Each rename proven from the OS build (same code base, same BIOS loading) joins its profile's cores. The resolver folds either separator, and falls back to the emulator column when the core names a mode, a machine or a plugin of that program, only where its profile declares the folder's system: MAME documents no GameKing ROM. 109 unresolved names are 56, each one recorded with why in tests/test_games_index.py.
41 lines
1.5 KiB
YAML
41 lines
1.5 KiB
YAML
emulator: Pyxel
|
|
type: standalone
|
|
core_classification: game_engine
|
|
source: "https://github.com/kitao/pyxel"
|
|
upstream: "https://github.com/kitao/pyxel"
|
|
profiled_date: "2026-10-04"
|
|
source_commit: "5d8e7b4f37c106684c1e91692772569a32a5e3d4"
|
|
core_version: "v2.9.9"
|
|
version_basis:
|
|
kind: tag
|
|
tag: "v2.9.9"
|
|
distance: 0
|
|
display_name: "Pyxel"
|
|
cores: [pyxel, "mf", "pixel2"]
|
|
systems: []
|
|
verification: existence
|
|
|
|
notes: |
|
|
Retro game engine for Python by Takashi Kitao. The engine is a Python
|
|
package with a Rust-based extension (crates/pyxel-core, built via maturin).
|
|
Pyxel programs are either .py scripts that import pyxel or self-contained
|
|
.pyxapp bundles (zip archives containing a startup script plus assets).
|
|
|
|
There is no external BIOS, firmware, or retail data to collect. Everything
|
|
the engine needs ships inside the Python wheel:
|
|
python/pyxel/: Python API, fonts, shader, examples
|
|
crates/pyxel-core/: Rust engine (compiled as pyxel_extension)
|
|
crates/pyxel-platform/: SDL2 wrapper
|
|
crates/pyxel-wrapper/: Python to Rust glue (PyO3)
|
|
|
|
Batocera's packaging (package/batocera/emulators/python-pyxel/python-pyxel.mk)
|
|
installs the wheel into site-packages, drops the examples, and provides a
|
|
pyxel.keys evmapy layout. The content run by Pyxel is the user's .pyxapp or
|
|
.py file, which plays the role of a cartridge. Those are user content, not
|
|
pack contents.
|
|
|
|
The engine refuses nothing on startup: a bare `pyxel init` plus a user
|
|
script is enough to run.
|
|
|
|
files: []
|