mirror of
https://github.com/libretro/libretro-super
synced 2024-11-28 11:14:11 +00:00
Some skeleton of how to USE libretro-super, kind of lame still.
This commit is contained in:
parent
c222ecbba1
commit
a4d6f0da91
@ -94,4 +94,17 @@ requirements.
|
|||||||
TODO: Works the same as libretro-super for Linux or under MSYS2 from here.
|
TODO: Works the same as libretro-super for Linux or under MSYS2 from here.
|
||||||
Document what that means exactly, later.
|
Document what that means exactly, later.
|
||||||
|
|
||||||
|
Nutshell version:
|
||||||
|
|
||||||
|
* ``git clone https://github.com/libretro/libretro-super.git && cd libretro-super``
|
||||||
|
or
|
||||||
|
``cd ~/path/to/libretro-super``
|
||||||
|
* ``./libretro-upgrade.sh``
|
||||||
|
* ``./libretro-fetch.sh``
|
||||||
|
* ``./libretro-build.sh``
|
||||||
|
|
||||||
|
You get the idea. You shouldn't need to run libretro-upgrade.sh after a fresh
|
||||||
|
clone—it's there to handle cross-module moves, renames, and deletions that git
|
||||||
|
cannot handle.
|
||||||
|
|
||||||
<!-- vim: set tw=78 ft=markdown: -->
|
<!-- vim: set tw=78 ft=markdown: -->
|
||||||
|
Loading…
Reference in New Issue
Block a user