Editing Libretro
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 11: | Line 11: | ||
|website = [http://www.libretro.com/ libretro.com]<br/>[https://twitter.com/Libretro Twitter] | |website = [http://www.libretro.com/ libretro.com]<br/>[https://twitter.com/Libretro Twitter] | ||
}} | }} | ||
+ | |||
'''libretro''' (formerly '''libsnes''') is an API designed mainly for games and emulators. It allows games and emulators to be compiled as dynamically linked libraries known as "libretro cores", which can be used in a frontend that implements libretro, such as [[RetroArch]]. The frontend is responsible for providing all the implementation specific details, such as video/audio/input drivers. This means that a developer does not have to worry about writing different video drivers for Direct3D or OpenGL, or supporting all known joypads or input/sound APIs. All of these details are handled by the front-end. | '''libretro''' (formerly '''libsnes''') is an API designed mainly for games and emulators. It allows games and emulators to be compiled as dynamically linked libraries known as "libretro cores", which can be used in a frontend that implements libretro, such as [[RetroArch]]. The frontend is responsible for providing all the implementation specific details, such as video/audio/input drivers. This means that a developer does not have to worry about writing different video drivers for Direct3D or OpenGL, or supporting all known joypads or input/sound APIs. All of these details are handled by the front-end. |