mirror of
https://github.com/Abdess/retroarch_system.git
synced 2026-11-11 12:33:53 -06:00
Abdessamad Derraz
cb7700a594
RetroPie writes dir_rom $romdir/mame-advmame:$romdir/arcade into the rc of each AdvanceMAME build (advmame.sh:100, configure_advmame being called by the 1.4 and 0.94 modules too). _search_list_in_roms split every list on ';', so the line was dropped and the sets landed at the BIOS root, where no build reads them. Each program's separator is now read from its own code: AdvanceMAME strtoks dir_rom on file_dir_separator(), ':' on Linux, in the three builds RetroPie ships (advance/linux/file.c:138-141, advance/osd/ fileio.c:696-699 at 96237a5, 685-688 at advancemame-1.4, 640-643 in advancemame-0.94.0). MAME splits on ';' (src/emu/fileio.cpp:56, 64, 112 at mame0289). RetroPie is rescraped at 427e762: the three passes_path records are its only change. advmame, advmame-1.4 and advmame-0.94 carry a retropie config_reads for dir_rom, read at the build RetroPie installs (96237a5, the tag advancemame-1.4 its tarball matches, the 0.94.0 tarball). The 1.4 and 0.94 profiles gain the dir_rom pool and a path for each set, and 0.94 a pin_build on rp_module_repo. Manifests: on RetroPie 55 sets of the three builds move from the BIOS root to roms/mame-advmame, the first folder of the list, which every game started from either folder reads. Seven archives other cores share stay at the root for them. No other platform changes. verify --all keeps its severity and status counts.