libretro / libretro/docs

https://docs.libretro.com/guides/download-cores/: Add a section how to manually download cores

Open
#912 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TeX
Stars
346
Forks
860
Avg merge
5d 16h
Merged PRs (30d)
7

Description

Describe the bug
https://docs.libretro.com/guides/download-cores/ doesn't have a section how to manually download, extract, and move a core to the core directory.

Example for GNU/Linux Appimage:

  • Download http://buildbot.libretro.com/nightly/linux/x86_64/latest/bsnes_hd_beta_libretro.so.zip
  • Extracted bsnes_hd_beta_libretro.so.zip
  • Moved bsnes_hd_beta_libretro.so to ~/Downloads//RetroArch-Linux-x86_64/RetroArch-Linux-x86_64.AppImage.home/.config/retroarch/cores/
  • ./RetroArch-Linux-x86_64.AppImage -L RetroArch-Linux-x86_64.AppImage.home/.config/retroarch/cores/bsnes_hd_beta_libretro.so "~/Downloads/Legend of Zelda, The - A Link to the Past (USA).sfc"

Expected behavior/changes
It would be useful if this was added.

Additional context
Add any other context about the problem here.

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 with the current https://docs.libretro.com/guides/download-cores/ page and review its existing core-download guidance. Add a manual-download section covering the GNU/Linux AppImage example: downloading and extracting the core, moving it to the core directory, and launching it with the shown command. Done means the page explains the workflow clearly for users who cannot use automatic core downloads.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, shell
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.