[Feature Request] Overlay content-directory system files over the configured system directory

Aperta
#20,105 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c
Ambito
backend

Direzione di ricerca

Start by tracing how systemfiles_in_content_dir selects the system directory and how the frontend reports missing firmware; the issue does not name specific source files or tests. Then check how session content load and unload manage temporary directories. Done means the core sees a merged view with content files taking precedence, original BIOS files remain protected, firmware reporting agrees, and fallback uses the configured directory.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

feature request

Summary

Add an optional system-files mode that combines the configured System/BIOS directory with the directory containing the loaded content, instead of replacing one directory with the other.

Problem

Currently, systemfiles_in_content_dir makes RetroArch provide the content directory as the system directory to the core. This is useful for game-specific firmware, but the core then no longer sees files that are only present in the configured System/BIOS directory. Users must either duplicate BIOS files beside content or choose between the global directory and the content directory.

Proposed behavior

Provide a separate mode (or extend the setting with a clearly defined mode) that presents a merged view of both directories to the core:

  • Files from the configured System/BIOS directory remain available.
  • Files in the content directory are overlaid on top of the configured directory; if both contain the same relative path/name, the content-directory file takes precedence.
  • The original BIOS files are never modified or replaced.
  • The core still receives one system-directory path through the existing libretro environment interface.
  • When no content is loaded, or the content directory cannot be determined, fall back to the configured System/BIOS directory.

For example, if the configured directory contains a, b, and c, and the game directory contains a replacement b, the core should see a, the content-specific b, and c.

Implementation considerations

RetroArch could construct a temporary merged directory for the session, using copies, links, or another portable mechanism, and clean it up when the content is unloaded. Any implementation should avoid writes from a core modifying the original BIOS files. Firmware/missing-BIOS reporting should use the same merged-directory and precedence rules so it agrees with what the core can actually access. The behavior should also be documented as distinct from the existing mode that uses only the content directory.

Benefits

This allows users to keep shared BIOS files in one central location while selectively supplying per-game firmware variants without duplicating all BIOS files or changing the global system directory.

Lingua principale
C
Stelle
14.6k
Fork
2.4k
Merge medio
2g 5h
PR unite (30g)
63

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di libretro/RetroArch

Tutte le issue di libretro/RetroArch

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.