mirror of
https://github.com/Abdess/retroarch_system.git
synced 2026-10-24 04:39:06 -05:00
Abdessamad Derraz
2927c49734
Reading this project's own reports gets its own page. Checker code is linked at the revision each platform list was read from. Installer moves to Your setup, legal to Start here, build internals to Contribute, and Reference pages carry a group.
3.2 KiB
3.2 KiB
level, order
| level | order |
|---|---|
| reference | 0 |
Reference
These pages describe how the files are checked, what the data holds and how the toolchain works. To set up BIOS files on a device, start with Get your files.
Checking files
- Find a file: any SHA1, MD5, CRC32 or SHA256 gives the file, the platforms that declare it and the emulators that check it
- How each platform checks files: existence, MD5 and SHA1 modes, severity matrix, resolution chain
- Reading this project's own reports:
verify.pyoutput, status codes and severity levels - What the packs do not hold: files emulators load that no pack can carry yet, by platform and by emulator
- Cores by platform: every core each platform runs, the systems it emulates, the upstream project it comes from
- Dump provenance: how the collection lines up against the No-Intro, Redump and TOSEC catalogs
Data
- Data and API: JSON, CSV and SQLite exports with their checksums
- Data model: database.json structure, indexes, file resolution order, YAML formats
- Updated platform files: each platform's own file, with the changes the emulator source supports
- Projects using this data: projects built on RetroBIOS data
Questions
- Technical questions: multiple hashes, MAME versions, UNTESTED, dump verification
Methodology
Platform lists are checked against emulator source code, file by file where a profile exists. Documentation and metadata can differ from what a program does at run time, so the source is the primary reference:
- Upstream emulator source: what the original project loads (Dolphin, PCSX2, Mednafen and others)
- Libretro core source: the RetroArch port, which may adapt paths or add files
.infodeclarations: metadata that platforms rely on, checked against the two above
For contributors
- Profiling guide: create an emulator profile from source code, YAML field reference
- Adding a platform: scraper, registry, YAML config, exporter, target scraper, install detection
- Adding a scraper: plugin architecture, BaseScraper, parsers, target scrapers
- Testing guide: run tests, fixture pattern, how to add tests, CI integration
- Release process: CI workflows, large files, manual release
- Architecture: directory structure, data flow, platform inheritance, pack grouping, security, edge cases, CI workflows
- Command-line tools: every script, pipeline usage, scrapers
- Build your own packs: custom packs, region filtering, one file per slot, target filtering, truth generation, emulator verification, offline workflow
See contributing for submission guidelines.
Terms
The words these pages use, from profile to provenance, are in Terms of the reference pages. The everyday words are in Words used on this site.