diff options
| author | Hunter Sezen <ovariegata@yahoo.com> | 2016-10-13 13:29:22 +0700 |
|---|---|---|
| committer | Willy Sudiarto Raharjo <willysr@slackbuilds.org> | 2016-10-13 13:29:22 +0700 |
| commit | 3b59088fec9cad4accda7f38b202fa18ae62ba82 (patch) | |
| tree | 7a9d4c979381939d450f65149bd7bb77fbef6c08 /games/GLupeN64/README | |
| parent | cc34580269ba3fff40e966ca5ca16b219707d47b (diff) | |
| download | slackbuilds-3b59088fec9cad4accda7f38b202fa18ae62ba82.tar.gz | |
games/GLupeN64: Updated for version 2016.10.12_4378f48.
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'games/GLupeN64/README')
| -rw-r--r-- | games/GLupeN64/README | 22 |
1 files changed, 8 insertions, 14 deletions
diff --git a/games/GLupeN64/README b/games/GLupeN64/README index 756b832c28..5b06c96018 100644 --- a/games/GLupeN64/README +++ b/games/GLupeN64/README @@ -1,22 +1,16 @@ -GLupeN64 is mupen64plus + RSP-HLE + GLideN64 + libretro. +GLupeN64 is mupen64plus + GLideN64 + libretro. How is this different from mupen64plus-libretro? -mupen64plus-libretro tries to emulate the complete mupen64plus experience -(think multiple graphic and RSP plugins). They also make modifications to -the code as they see fit. +mupen64plus-libretro implements multiple Graphics plugins. There are also +code modifications that make it different than standalone mupen64plus. -Because mupen64plus is built to be modular it is difficult to "convert" -that project to a libretro core, since you end up with functions with the -same name (for instance multiple functions named "PluginStartup"). +GLupeN64 uses GLideN64 (a graphics plugin that is not available in +mupen64plus-libretro). The emulator code itself is identical to +standalone mupen64plus. -Many modifications had to be made to the mupen64plus-libretro code to get -it to work inside libretro. As a result, it differs quite greatly from vanilla -mupen64plus (there is no up to date GLideN64 implmentation for example). - -By choosing one RSP implentation (rsp-hle) and one graphics plugin (GLideN64), -we will be able to keep the code in line with upstream, and maintaining the -code will be much simpler. +By choosing one graphics plugin (GLideN64), we will be able to keep the +code in line with upstream, and maintaining the code will be much simpler. To build the debugging symbols use: DEBUG=1 ./GLupeN64.SlackBuild |