libretro / libretro/RetroArch

[ Suggestion ] Move Windows (and other platforms?) default 'info' location to 'cores' dir

Open
#11,621 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

The core info files currently live in a separate directory in Windows (but not in Linux) from the cores themselves. If they lived in the same location, it would be very easy to bundle info files in the repo with the core libs themselves, which would have the advantages of giving core authors more direct control over the content of the info files, remove the need to update them in a second location (i.e., the libretro-super repo) and allow updating both the core and the info with a single download from the core downloader. This also means that new cores come with their info file without needing to download it separately (though it will still have the ugly filename until the first download).

The downside is that it's messier having them both live in the same location.

I discussed this with @m4xw and @XerTheSquirrel in discord the other day, but it is pertinent to the ongoing new automated build setup.

Expected behavior

Core and info files live in the same location

Actual behavior

they are separate

Steps to reproduce the bug
  1. download a core
  2. have an old (or nonexistent) info file
Bisect Results

always

Version/Commit

all

  • RetroArch: all
Environment information
  • OS: Windows
  • Compiler: unrelated

@twinaphex

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing RetroArch's Windows core and info-file locations and the core downloader, then compare how the paths are handled on Linux and other platforms. Review the ongoing automated build setup mentioned in the issue; done means core and info files use the same location without breaking downloads or platform-specific behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.