Libretro - Revision history

Karellen at 21:24, 21 May 2020

2020-05-21T21:24:55Z

← Older revision		Revision as of 21:24, 21 May 2020
Line 65:		Line 65:
	** [[Game development]] - A guide to developing games for Kodi		** [[Game development]] - A guide to developing games for Kodi
	** [[Compiling Kodi-Game\|Compiling Kodi with RetroPlayer]]		** [[Compiling Kodi-Game\|Compiling Kodi with RetroPlayer]]
	** [[~~Compiling game add~~-~~ons~~\|Compiling existing game add-ons]]		** [[Compiling_Kodi-Game\|Compiling existing game add-ons]]

	=External Links=		=External Links=

Jaylinski: Fix typo

2020-03-21T17:48:49Z

Fix typo

← Older revision		Revision as of 17:48, 21 March 2020
Line 26:		Line 26:

	=Libretro GL/GLES/Vulkan=		=Libretro GL/GLES/Vulkan=
	Aside from retro-style games and emulators that depend on software rendering and where you’d typically need nothing more than the ability to render to a framebuffer, the Libretro API also allows you to target OpenGL, OpenGL ES (GLES), and Vulkan. This allows you to create libretro ports that use OpenGL, OpenGL ES (GLES), or ~~Vulkanas~~ part of their internal rendering.		Aside from retro-style games and emulators that depend on software rendering and where you’d typically need nothing more than the ability to render to a framebuffer, the Libretro API also allows you to target OpenGL, OpenGL ES (GLES), and Vulkan. This allows you to create libretro ports that use OpenGL, OpenGL ES (GLES), or Vulkan as part of their internal rendering.

	From a portability perspective, we highly recommend that you try to target both so that your libretro GL port will work on both mobile (OpenGL ES) and desktop (OpenGL) computers.		From a portability perspective, we highly recommend that you try to target both so that your libretro GL port will work on both mobile (OpenGL ES) and desktop (OpenGL) computers.

Gamester17: /* See also */

2018-10-26T12:53:00Z

Gamester17: /* What is libretro? */

2018-10-26T12:40:31Z

What is libretro?

← Older revision		Revision as of 12:40, 26 October 2018
Line 18:		Line 18:
	Any project that is ported to work with this API can be made to run on ANY libretro frontend – now and forever. You maintain a single codebase that only deals with the main program, and you then target one single API (libretro) in order to port your program over to multiple platforms at once.		Any project that is ported to work with this API can be made to run on ANY libretro frontend – now and forever. You maintain a single codebase that only deals with the main program, and you then target one single API (libretro) in order to port your program over to multiple platforms at once.

	Other projects benefit from our ever-expanding libretro core software library by implementing the libretro API inside their own projects. To this end, project such as Kodi (XBMC Foundation) have written a libretro driver which follows the same concept as the reference libretro frontend, RetroArch.		Other projects benefit from our ever-expanding libretro core software library by implementing the libretro API inside their own projects. To this end, project such as Kodi (XBMC Foundation) have written a libretro wrapper/driver which follows the same concept as the reference libretro frontend, RetroArch.

	Kodi's (with RetroPlayer) is frontend for Libretro. RetroArch is the official reference frontend, and it is only for gaming and is meant to be fast, simple, yet powerful, and is available on nearly all modern-day platforms. Other third-party platform-specific frontends for Libretro are currently in development, including Arcan and Minir. For more checkout: https://www.libretro.com/index.php/powered-by-libretro/		Kodi's (with RetroPlayer) is frontend for Libretro. RetroArch is the official reference frontend, and it is only for gaming and is meant to be fast, simple, yet powerful, and is available on nearly all modern-day platforms. Other third-party platform-specific frontends for Libretro are currently in development, including Arcan and Minir. For more checkout: https://www.libretro.com/index.php/powered-by-libretro/

Gamester17: /* What is libretro? */

2018-10-26T12:39:59Z

What is libretro?

← Older revision		Revision as of 12:39, 26 October 2018
Line 18:		Line 18:
	Any project that is ported to work with this API can be made to run on ANY libretro frontend – now and forever. You maintain a single codebase that only deals with the main program, and you then target one single API (libretro) in order to port your program over to multiple platforms at once.		Any project that is ported to work with this API can be made to run on ANY libretro frontend – now and forever. You maintain a single codebase that only deals with the main program, and you then target one single API (libretro) in order to port your program over to multiple platforms at once.

	Other projects benefit from our ever-expanding libretro core software library by implementing the libretro API inside their own projects. To this end, project such as XBMC have ~~already begun writing~~ a libretro driver ~~based on~~ the ~~RetroArch~~ reference libretro frontend.		Other projects benefit from our ever-expanding libretro core software library by implementing the libretro API inside their own projects. To this end, project such as Kodi (XBMC Foundation) have written a libretro driver which follows the same concept as the reference libretro frontend, RetroArch.

	Kodi's (with RetroPlayer) is frontend for Libretro. RetroArch is the official reference frontend, and it is only for gaming and is meant to be fast, simple, yet powerful, and is available on nearly all modern-day platforms. Other third-party platform-specific frontends for Libretro are currently in development, including Arcan and Minir. For more checkout: https://www.libretro.com/index.php/powered-by-libretro/		Kodi's (with RetroPlayer) is frontend for Libretro. RetroArch is the official reference frontend, and it is only for gaming and is meant to be fast, simple, yet powerful, and is available on nearly all modern-day platforms. Other third-party platform-specific frontends for Libretro are currently in development, including Arcan and Minir. For more checkout: https://www.libretro.com/index.php/powered-by-libretro/

Gamester17 at 12:36, 26 October 2018

2018-10-26T12:36:23Z

← Older revision		Revision as of 12:36, 26 October 2018
Line 12:		Line 12:
	Download the [http://www.libretro.com/wp-content/uploads/2014/03/RetroArch-Libretro-Technical-Brochure.pdf RetroArch/Libretro Technical Brochure (PDF) from libretro.org website]		Download the [http://www.libretro.com/wp-content/uploads/2014/03/RetroArch-Libretro-Technical-Brochure.pdf RetroArch/Libretro Technical Brochure (PDF) from libretro.org website]

	Libretro is a simple API that allows for the creation of games and emulators. It is very simple in nature, yet very powerful. The simplicity of it all requires some explanation in order to truly grasp how useful it can be to your own projects.		Libretro is a simple lightweight C/C++ API that allows for the creation of games and emulators. It is very simple in nature, yet very powerful. The simplicity of it all requires some explanation in order to truly grasp how useful it can be to your own projects. It works according to backend/frontend principle. Backend application talks with frontend by way of API. Facilitates input/audio/video/camera/location streams for use in games/media-players/graphics applications. With added value (shaders, rewinding, input support, etc).

	When you choose to use the libretro API, your program gets turned into a single library file (called a ‘libretro core’). A frontend that supports the libretro API can then load that library file and run the app. The frontend’s responsibility is to provide all the implementation-specific details, such as video/audio/input drivers. The libretro core’s responsibility is solely to provide the main program. You therefore don’t have to worry about writing different video drivers for Direct3D, OpenGL or worrying about catering to all possible input APIs/sound APIs/supporting all known joypads/etc. This is none of your concern at the libretro core implementation level.		When you choose to use the libretro API, your program gets turned into a single library file (called a ‘libretro core’). A frontend that supports the libretro API can then load that library file and run the app. The frontend’s responsibility is to provide all the implementation-specific details, such as video/audio/input drivers. The libretro core’s responsibility is solely to provide the main program. You therefore don’t have to worry about writing different video drivers for Direct3D, OpenGL or worrying about catering to all possible input APIs/sound APIs/supporting all known joypads/etc. This is none of your concern at the libretro core implementation level.
Line 20:		Line 20:
	Other projects benefit from our ever-expanding libretro core software library by implementing the libretro API inside their own projects. To this end, project such as XBMC have already begun writing a libretro driver based on the RetroArch reference libretro frontend.		Other projects benefit from our ever-expanding libretro core software library by implementing the libretro API inside their own projects. To this end, project such as XBMC have already begun writing a libretro driver based on the RetroArch reference libretro frontend.

	RetroArch is the official reference frontend, and it is ~~available on nearly all modern-day platforms. It~~ is meant to be fast, simple, yet powerful.		Kodi's (with RetroPlayer) is frontend for Libretro. RetroArch is the official reference frontend, and it is only for gaming and is meant to be fast, simple, yet powerful, and is available on nearly all modern-day platforms. Other third-party platform-specific frontends for Libretro are currently in development, including Arcan and Minir. For more checkout: https://www.libretro.com/index.php/powered-by-libretro/

	Other platform-specific frontends are currently in development, including ~~native integration with the popular HTPC platform XBMC~~.

	=Who Uses Libretro?=		=Who Uses Libretro?=
Line 48:		Line 46:

	===Some of the design goals for libretro===		===Some of the design goals for libretro===

	: * Allow a non-kitchensink approach to crossplatform portability.		: * Allow a non-kitchensink approach to crossplatform portability.
	: * Allow a non-dependency heavy approach to crossplatform portability. Stick to just one header containing definitions for the necessary audio/video/input callbacks.		: * Allow a non-dependency heavy approach to crossplatform portability. Stick to just one header containing definitions for the necessary audio/video/input callbacks.

Gamester17: /* Libretro GL/GLES/Vulkan */

2018-10-26T10:37:04Z

Libretro GL/GLES/Vulkan

← Older revision		Revision as of 10:37, 26 October 2018
Line 28:		Line 28:

	=Libretro GL/GLES/Vulkan=		=Libretro GL/GLES/Vulkan=
	Aside from retro-style games and emulators that depend on software rendering and where you’d typically need nothing more than the ability to render to a framebuffer, the Libretro API also allows you to target OpenGL, OpenGL ES, and Vulkan. This allows you to create libretro ports that use OpenGL, OpenGL ES, or Vulkanas part of their internal rendering.		Aside from retro-style games and emulators that depend on software rendering and where you’d typically need nothing more than the ability to render to a framebuffer, the Libretro API also allows you to target OpenGL, OpenGL ES (GLES), and Vulkan. This allows you to create libretro ports that use OpenGL, OpenGL ES (GLES), or Vulkanas part of their internal rendering.

	From a portability perspective, we highly recommend that you try to target both so that your libretro GL port will work on both mobile (OpenGL ES) and desktop (OpenGL) computers.		From a portability perspective, we highly recommend that you try to target both so that your libretro GL port will work on both mobile (OpenGL ES) and desktop (OpenGL) computers.

Gamester17: /* Libretro GL/Vulkan */

2018-10-26T10:36:35Z

Libretro GL/Vulkan

← Older revision		Revision as of 10:36, 26 October 2018
Line 27:		Line 27:
	While the most common use case for libretro has been console emulation, it is equally suited as a platform for almost any 2D game. For example, the NX Engine used in the popular freeware game Cave Story has been successfully ported to libretro, open sourced games like Quake and Doom have been ported to libretro, and the new freeware game Dinothawr supports libretro natively.		While the most common use case for libretro has been console emulation, it is equally suited as a platform for almost any 2D game. For example, the NX Engine used in the popular freeware game Cave Story has been successfully ported to libretro, open sourced games like Quake and Doom have been ported to libretro, and the new freeware game Dinothawr supports libretro natively.

	=Libretro GL/Vulkan=		=Libretro GL/GLES/Vulkan=
	Aside from retro-style games and emulators that depend on software rendering and where you’d typically need nothing more than the ability to render to a framebuffer, the Libretro API also allows you to target OpenGL and Vulkan. This allows you to create libretro ports that use OpenGL or Vulkanas part of their internal rendering.		Aside from retro-style games and emulators that depend on software rendering and where you’d typically need nothing more than the ability to render to a framebuffer, the Libretro API also allows you to target OpenGL, OpenGL ES, and Vulkan. This allows you to create libretro ports that use OpenGL, OpenGL ES, or Vulkanas part of their internal rendering.

	From a portability perspective, we highly recommend that you try to target both so that your libretro GL port will work on both mobile and desktop computers.		From a portability perspective, we highly recommend that you try to target both so that your libretro GL port will work on both mobile (OpenGL ES) and desktop (OpenGL) computers.

	=Why Should Developers Target Libretro?=		=Why Should Developers Target Libretro?=

Gamester17 at 10:35, 26 October 2018

2018-10-26T10:35:04Z

← Older revision		Revision as of 10:35, 26 October 2018
Line 1:		Line 1:
	{{mininav\| [[Kodi Game]] }}		{{mininav\| [[Kodi Game]] }}

			Kodi's Game API has Libretro Wrapper which is 1:1 compatibility with the libretro API, and all libretro cores can be ported game add-ons for Kodi. Libretro itself is a well defined cross-platform platform interface to handle the communication between a frontend (Kodi with RetroPlayer) and an Emulator Core (e.g. nestopia). Kodi uses libretro but libretro is its own seperate open source project developed by independent developers.

	:{{Main\|Game add-ons\|Game development}}		:{{Main\|Game add-ons\|Game development}}

	Kodi's Game API has Libretro Wrapper which is 1:1 compatibility with the libretro API, and all libretro cores can be ported game add-ons for Kodi. Libretro itself is a well defined cross-platform platform interface to handle the communication between a frontend (Kodi with RetroPlayer) and an Emulator Core (e.g. nestopia). Kodi uses libretro but libretro is its own seperate open source project developed by independent developers.

	For more detailed information about libretro please visit their website at:		For more detailed information about libretro please visit their website at:
	:* https://www.libretro.com/index.php/api/		* https://www.libretro.com/index.php/api/

Gamester17 at 10:34, 26 October 2018

2018-10-26T10:34:08Z

← Older revision		Revision as of 10:34, 26 October 2018
Line 1:		Line 1:
			{{mininav\| [[Kodi Game]] }}

	:{{Main\|Game add-ons\|Game development}}		:{{Main\|Game add-ons\|Game development}}

← Older revision		Revision as of 12:53, 26 October 2018
Line 59:		Line 59:
	** [[Game management]] - A guide to managing game files for and in Kodi		** [[Game management]] - A guide to managing game files for and in Kodi
	*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi		*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
			**[[Game add-ons]]
			*** [[Porting Libretro cores to game add-ons]]
			**** [[Libretro]]
	*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi		*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
	** [[Game development]] - A guide to developing games for Kodi		** [[Game development]] - A guide to developing games for Kodi
	** [[Compiling Kodi-Game\|Compiling Kodi with RetroPlayer]]		** [[Compiling Kodi-Game\|Compiling Kodi with RetroPlayer]]
	** [[Compiling game add-ons\|Compiling existing game add-ons]]		** [[Compiling game add-ons\|Compiling existing game add-ons]]
	** [[Porting Libretro cores to game add-ons]]

	=External Links=		=External Links=