provide a way for cores with need_fullpath==false to determine content filename
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start with libretro.h and the definitions of retro_game_info, need_fullpath, and existing callbacks. Compare the two API options described in the issue with the linked PR clarifying existing behavior; done means cores can determine the content filename when need_fullpath is false through an agreed API behavior.
Written by the indexing model from the issue text.
Description
Many cores create save and configuration files which are named based on the filename of the content they are executing.
When a core sets need_fullpath==false, there is no means specified in libretro.h for the core to determine the filename so there is no way to name the save files. @fr500 provides an example of this issue from beetle-gba here: https://github.com/libretro/beetle-gba-libretro/pull/33#issuecomment-406910261
I'm creating this issue because it seems separate from the PR I submitted to clarify the existing behavior.
Two possible ways I can think of to provide the name of the content to the core are:
- update the API so that
if need_fullpath == falsethenretro_game_info::pathwill return the filename of the content (not the full path) - create a new callback which returns the name of the content
- Dominant language
- C
- Stars
- 182
- Forks
- 98
- Avg merge
- 14d 4h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libretro/libretro-common
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libretro/libretro-common#220 · 1 comment · 1 reaction ·
-
RETRO_ENVIRONMENT_ clash in libretro.hMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretro/libretro-common#89 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
libretro/libretro-common#223 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
libretro/libretro-common#221 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
libretro/libretro-common#213 ·
All issues in libretro/libretro-common
Similar issues
-
dependency component: oneMKL module: dpclang
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
intel/torch-xpu-ops#5880 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
CVE-2026-111497Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
fink/fink-distributions#1322 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
openvehicles/Open-Vehicle-Monitoring-System-3#1563 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100