Compiling and installing link has outdated instructions
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 link given in the readme here leads to outdated instructions.
`git clone git://github.com/libretro/libretro-super.git
cd libretro-super
SHALLOW_CLONE=1 ./libretro-fetch.sh
./retroarch-build.sh
NOCLEAN=1 ./libretro-build.sh
mkdir -p /ra/cores/ra install
cd retroarch
make DESTDIR=
cd .. #to libretro-super directory
./libretro-install.sh ~/ra/cores`
Expected behavior
I expected it to compile
Actual behavior
The github link is wrong.
There is no retroarch-build.sh
Nothing happens.
Steps to reproduce the bug
- Go to https://github.com/libretro/RetroArch
- Scroll down to Compiling and installing
- Click the link labeled "[Libretro/RetroArch Documentation Center."
- Click link labeled "For Developers"
- Click link labeled "RetroArch Development"
- Click link labeled "RetroArch Compilation Guides"
- Click link labeled "Linux and BSD"
- Click link labeled "Overview for Linux/BSD"
- Use bash code from page:
`git clone git://github.com/libretro/libretro-super.git
cd libretro-super
SHALLOW_CLONE=1 ./libretro-fetch.sh
./retroarch-build.sh
NOCLEAN=1 ./libretro-build.sh
mkdir -p /ra/cores/ra install
cd retroarch
make DESTDIR=
cd .. #to libretro-super directory
./libretro-install.sh ~/ra/cores`
Version/Commit
- RetroArch: 1.10.3
Environment information
- OS: funtoo/gentoo
- Compiler: gcc
Contributor guide
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.
Research direction
Start at the RetroArch README's “Compiling and installing” link and follow the referenced Linux/BSD compilation guide. Check the listed libretro-super commands against the current repository instructions, then update the outdated link and commands so the documented process reaches a successful compilation and installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, git
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100