You may encounter problems if running on a CLI or a display server other than Xorg or if you use the udev input driver, because /dev/input nodes are limited to root-only access. Reason: We might want to update this section to point to Udev#Allowing regular users to use devices? (Discuss in Talk:RetroArch) Libretro_directory = "/usr/lib/libretro" ~/.config/retroarch/retroarch.cfg #include "/etc/retroarch.cfg" Libretro_info_path = "/usr/share/libretro/info" etc/retroarch.cfg # for retroarch-assets-xmbĪssets_directory = "/usr/share/retroarch/assets" If you install any RetroArch components system-wide with pacman, you should specify these in the global configuration file and include them in your user file. Libretro_info_path = "~/.config/retroarch/cores/info" ~/.config/retroarch/retroarch.cfg libretro_directory = "~/.config/retroarch/cores" If you install RetroArch components in your home-directory, you should specify local paths in the global configuration file for downloading cores. When you first run RetroArch it will create the user configuration file ~/.config/retroarch/retroarch.cfg. $ retroarch -libretro /path/to/some_core_libretro.so /path/to/rom Configuration Change your #Configuration if you install them elsewhere. These can be downloaded per-user within RetroArch itself (via the libretro Buildbot) or you can install them system-wide with libretro or AUR.īy default RetroArch is configured to load the per-user cores that it downloads. RetroArch relies on separate libraries, called "cores", for most of its functionality. Install retroarch-standalone-service AUR to get system user, system service and RetroArch configuration for standalone game-box.You may also want to install retroarch-assets-ozone for a more desktop-friendly GUI. Install retroarch-assets-xmb to get the fonts and icons for the RetroArch GUI.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |