| Both sides previous revision Previous revision Next revision | Previous revision |
| notable_files [2022/02/21 08:38] – added link to updated list of themes for content downloader atari | notable_files [2023/01/09 15:51] (current) – [Batocera bundled content] lbrpdx |
|---|
| |
| ^ File purpose ^ Github source location ^ Final image location (x86_64) ^ Notes ^ | ^ File purpose ^ Github source location ^ Final image location (x86_64) ^ Notes ^ |
| | Config generators (emulator defaults) | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core/batocera-configgen/configgen/configgen/generators | ''/usr/lib/python3.9/site-packages/configgen/generators/'' | The infamous Python configuration generators, bane of the end-user who's used to modifying INI and XML files directly. These are what create the necessary configuration files, controller profiles and any other necessary INI/CFG file an emulator uses upon launching an emulator. Used in conjunction with [[#emulationstation_options|ES advanced per-system options]] to make these generated configs based on the options the user has set in ES. If creating a new one, don't forget to [[#batocera-specific_data_meta_information|define it]] as well. | | | Config generators (emulator defaults) | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core/batocera-configgen/configgen/configgen/generators | ''/usr/lib/python#.#/site-packages/configgen/generators/'' | The infamous Python configuration generators, bane of the end-user who's used to modifying INI and XML files directly. These are what create the necessary configuration files, controller profiles and any other necessary INI/CFG file an emulator uses upon launching an emulator. Used in conjunction with [[#emulationstation_options|ES advanced per-system options]] to make these generated configs based on the options the user has set in ES. If creating a new one, don't forget to [[#batocera-specific_data_meta_information|define it]] as well. | |
| | Emulator launch command array generator | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/emulationstation/batocera-es-system/batocera-es-system.py | Generates ''/usr/share/emulationstation/es_systems.cfg'' and ''es_features.cfg'' | This one generates the run command (command array) that is written to ''/usr/share/emulationstation/es_systems.cfg'' in the final image. | | | Emulator launch command array generator | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/emulationstation/batocera-es-system/batocera-es-system.py | Generates ''/usr/share/emulationstation/es_systems.cfg'' and ''es_features.cfg'' | This one generates the run command (command array) that is written to ''/usr/share/emulationstation/es_systems.cfg'' in the final image. | |
| | Emulator config generator | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core/batocera-configgen/configgen/configgen/generators followed by /<system name>/<system name>Generator.py | ''/usr/lib/python3.9/site-packages/configgen/generators/<system name>/<system name>Generator.py'' | The "main" generator script for an emulator. This is the file that is specified by the [[#batocera-specific_data_meta_information|emulator launcher specifier]]. This script can be separated into multiple scripts that call upon each other to separate and better organize the code. | | | Emulator config generator | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core/batocera-configgen/configgen/configgen/generators followed by /<system name>/<system name>Generator.py | ''/usr/lib/python3.9/site-packages/configgen/generators/<system name>/<system name>Generator.py'' | The "main" generator script for an emulator. This is the file that is specified by the [[#batocera-specific_data_meta_information|emulator launcher specifier]]. This script can be separated into multiple scripts that call upon each other to separate and better organize the code. | |
| |
| ^ File purpose ^ Github source location ^ Final image location (x86_64) ^ Notes ^ | ^ File purpose ^ Github source location ^ Final image location (x86_64) ^ Notes ^ |
| | RetroArch main generator | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-configgen/configgen/configgen/generators/libretro/libretroGenerator.py | ''/usr/lib/python3.9/site-packages/configgen/generators/libretro/libretroGenerator.py'' | Calls all the other libretro-related generator files and produces the final command array. | | | RetroArch main generator | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-configgen/configgen/configgen/generators/libretro/libretroGenerator.py | ''/usr/lib/python#.#/site-packages/configgen/generators/libretro/libretroGenerator.py'' | Calls all the other libretro-related generator files and produces the final command array. | |
| | RetroArch configuration file | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-configgen/configgen/configgen/generators/libretro/libretroConfig.py | ''/usr/lib/python3.9/site-packages/configgen/generators/libretro/libretroRetroarchCustom.py'', generates ''/userdata/system/.configs/retroarch/retroarchcustom.cfg'' upon drive initialization | RetroArch's main settings files. Includes input settings. The user can also manually edit in certain values to this file using RetroArch's "save configuration" or by hand, but most values get overwritten by this config generator. | | | RetroArch configuration file | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-configgen/configgen/configgen/generators/libretro/libretroConfig.py | ''/usr/lib/python#.#/site-packages/configgen/generators/libretro/libretroRetroarchCustom.py'', generates ''/userdata/system/.configs/retroarch/retroarchcustom.cfg'' upon drive initialization | RetroArch's main settings files. Includes input settings. The user can also manually edit in certain values to this file using RetroArch's "save configuration" or by hand, but most values get overwritten by this config generator. | |
| | RetroArch custom configuration generator | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-configgen/configgen/configgen/generators/libretro/libretroRetroarchCustom.py | ''/usr/lib/python3.9/site-packages/configgen/generators/libretro/libretroRetroarchCustom.py'', writes to ''/userdata/system/.config/retroarch/retroarchcustom.cfg'' as well | Appends all of Batocera's necessary settings to ''retroarchcustom.cfg''. If a user has manually placed settings here that conflict with Batocera's required ones, they will be overwritten by this script. | | | RetroArch custom configuration generator | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-configgen/configgen/configgen/generators/libretro/libretroRetroarchCustom.py | ''/usr/lib/python#.#/site-packages/configgen/generators/libretro/libretroRetroarchCustom.py'', writes to ''/userdata/system/.config/retroarch/retroarchcustom.cfg'' as well | Appends all of Batocera's necessary settings to ''retroarchcustom.cfg''. If a user has manually placed settings here that conflict with Batocera's required ones, they will be overwritten by this script. | |
| | RetroArch core options | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-configgen/configgen/configgen/generators/libretro/libretroOptions.py | ''/usr/lib/python3.9/site-packages/configgen/generators/libretro/libretroOptions.py'', generates and saves to ''/userdata/system/configs/retroarch/cores/retroarch-core-options.cfg'' upon emulator launch | The default core options that RetroArch uses based on the advanced per-system configuration set by the user in ''batocera.conf'' or ES. The user can also manually edit in certain values to this file using RetroArch's "save configuration" or by hand, but most values get overwritten by this config generator. If you're adding a Libretro core, you'll likely need to edit this file (unless the core has no core options). | | | RetroArch core options | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-configgen/configgen/configgen/generators/libretro/libretroOptions.py | ''/usr/lib/python#.#/site-packages/configgen/generators/libretro/libretroOptions.py'', generates and saves to ''/userdata/system/configs/retroarch/cores/retroarch-core-options.cfg'' upon emulator launch | The default core options that RetroArch uses based on the advanced per-system configuration set by the user in ''batocera.conf'' or ES. The user can also manually edit in certain values to this file using RetroArch's "save configuration" or by hand, but most values get overwritten by this config generator. If you're adding a Libretro core, you'll likely need to edit this file (unless the core has no core options). | |
| | RetroArch core option overrides | N/A, created by the user | ''/userdata/system/.config/retroarch/config/'', created when the user saves core options in RetroArch | The core options saved by RetroArch. These have priority over ''batocera.conf''. | | | RetroArch core option overrides | N/A, created by the user | ''/userdata/system/.config/retroarch/config/'', created when the user saves core options in RetroArch | The core options saved by RetroArch. These have priority over ''batocera.conf''. | |
| | RetroArch controller input generator settings | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-configgen/configgen/configgen/generators/libretro/libretroControllers.py | ''/usr/lib/python3.9/site-packages/configgen/generators/libretro/libretroControllers.py'' | FIXME | | | RetroArch controller input generator settings | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-configgen/configgen/configgen/generators/libretro/libretroControllers.py | ''/usr/lib/python#.#/site-packages/configgen/generators/libretro/libretroControllers.py'' | How the "Retropad" and RetroArch's [[:basic_commands|hotkeys]] are configured. | |
| | RetroArch remap overrides | N/A, created by the user | ''/userdata/system/.config/retroarch/config/remaps/'', created when the user saves a custom remap in RetroArch | The controller remaps saved by the user. These have the highest priority of any settings generated by Batocera and thus becomes immune to changes/updates made to the input generator (with respects to the Retropad at least). | | | RetroArch remap overrides | N/A, created by the user | ''/userdata/system/.config/retroarch/config/remaps/'', created when the user saves a custom remap in RetroArch | The controller remaps saved by the user. These have the highest priority of any settings generated by Batocera and thus becomes immune to changes/updates made to the input generator (with respects to the Retropad at least). | |
| | Libretro cores | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/emulators/retroarch/libretro | Compiled to ''/usr/lib/libretro/'' | The compiled cores used by RetroArch. Binaries should not be directly placed here, only compiled during the build process. | | | Libretro cores | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/emulators/retroarch/libretro | Compiled to ''/usr/lib/libretro/'' | The compiled cores used by RetroArch. Binaries should not be directly placed here, only compiled during the build process. | |
| |
| ^ File purpose ^ Github source location ^ Final image location (x86_64) ^ Notes ^ | ^ File purpose ^ Github source location ^ Final image location (x86_64) ^ Notes ^ |
| | Batocera user config template | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-system/batocera.conf | ''/userdata/system/batocera.conf'' | FIXME | | | Batocera user config template | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-system/batocera.conf | ''/userdata/system/batocera.conf'' | The main configuration file of Batocera. It's not actually necessary to have anything in the file, as Batocera can function without needing any pre-configuration, however you may want to keep it for certain pre-configured settings like enabled Bluetooth and Wi-Fi (remember, Batocera was initially designed for low-powered handhelds and SBCs so these were the old defaults back in the day). | |
| | | Batocera boot template | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-system/batocera-boot.conf | ''/boot/batocera-boot.conf'' | Useful to look at this on the Github to see if any new keys/explanations have been added. | |
| | Batocera core directory | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core | Various, though most are in ''/usr/bin/'' | Where most of Batocera's core functionalities are! | | | Batocera core directory | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core | Various, though most are in ''/usr/bin/'' | Where most of Batocera's core functionalities are! | |
| | Batocera scripts | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core/batocera-scripts/scripts | ''/usr/bin/'' | Where most bash scripts are! These are the files you're calling when you run commands [[:access_the_batocera_via_ssh|via SSH]] or the terminal. | | | Batocera scripts | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core/batocera-scripts/scripts | ''/usr/bin/'' | Where most bash scripts are! These are the files you're calling when you run commands [[:access_the_batocera_via_ssh|via SSH]] or the terminal. | |
| | ES systems | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/emulationstation/batocera-es-system/es_systems.yml | [[#emulator_configuration|Recipe]] to ''/usr/share/emulationstation/es_features.cfg'', and defines which packages they depend on | Source to the CFG file created for ES for its configured systems. This is the one you'll have to add a new entry to if you've added a new emulator/system to Batocera. Also contains the information used to generate the ''_info.txt'' files in the ''/userdata/roms/'' directories. You can specify which platforms this emulator is included in with [[#board_patches|the included emulators config file]]. | | | ES systems | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/emulationstation/batocera-es-system/es_systems.yml | [[#emulator_configuration|Recipe]] to ''/usr/share/emulationstation/es_features.cfg'', and defines which packages they depend on | Source to the CFG file created for ES for its configured systems. This is the one you'll have to add a new entry to if you've added a new emulator/system to Batocera. Also contains the information used to generate the ''_info.txt'' files in the ''/userdata/roms/'' directories. You can specify which platforms this emulator is included in with [[#board_patches|the included emulators config file]]. | |
| | Supplementary emulator files | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/emulationstation/batocera-es-system/roms | FIXME | Extra files/folders required for the system. | | | Supplementary emulator files | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/emulationstation/batocera-es-system/roms | FIXME | Extra files/folders required for the system. | |
| | Batocera es_system generator | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/emulationstation/batocera-es-system/batocera-es-system.py | FIXME | Generates the es_systems.cfg file. Generates roms folder and emulators folders. Generate the _info.txt file with the emulator information. Information from the emulators are being extracted from the file es_system.yml | | | Batocera es_system generator | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/emulationstation/batocera-es-system/batocera-es-system.py | FIXME | Generates the ''es_systems.cfg'' file. Generates roms folder and emulators folders. Generate the ''_info.txt'' file with the emulator information. Information from the emulators are being extracted from the file ''es_system.yml'' | |
| | | BIOS file database | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-scripts/scripts/batocera-systems | FIXME | Catalogue of all the BIOS files for various emulators and their md5 checksums. | |
| | Batocera decorations generator | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-configgen/configgen/configgen/utils/bezels.py | FIXME | Generates the composite image used as the overlay (decoration). Recently, most of this was in libretro's configgen, but recent developments have made this independent of libretro. | | | Batocera decorations generator | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-configgen/configgen/configgen/utils/bezels.py | FIXME | Generates the composite image used as the overlay (decoration). Recently, most of this was in libretro's configgen, but recent developments have made this independent of libretro. | |
| | Compiled component configuration | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-system/Config.in | FIXME | This is where all the modules you want to compile with Batocera are specified. This can be used to exclude/include particular core utilities for certain platforms. | | | Compiled component configuration | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-system/Config.in | FIXME | This is where all the modules you want to compile with Batocera are specified. This can be used to exclude/include particular core utilities for certain platforms. | |
| | Batocera desktop shortcuts | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core/batocera-desktopapps | ''/usr/share/applications'' | The shortcuts shown in the [[:built_file_manager#applications_advanced_standalone_emulator_configuration|"Applications" in the file manager's sidebar]]. | | | Batocera desktop shortcuts | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core/batocera-desktopapps | ''/usr/share/applications'' | The shortcuts shown in the [[:built_file_manager#applications_advanced_standalone_emulator_configuration|"Applications" in the file manager's sidebar]]. | |
| | | Case switch scripts | Various folders in [[https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/utils]] (most are in [[https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/utils/rpigpioswitch]]) | ''/usr/bin/'' | The various [[:add_powerdevices_rpi_only|power devices and buttons]] that can be selected in ''batocera.conf'' | |
| |
| ===== Batocera bundled content ===== | ===== Batocera bundled content ===== |
| |
| ^ File purpose ^ Github source location ^ Final image location (x86_64) ^ Notes ^ | ^ File purpose ^ Github source location ^ Final image location (x86_64) ^ Notes ^ |
| | Skeleton directory structure | Various scripts copy files to ''datainit'' during compilation | ''/usr/share/batocera/datainit/'' | The skeleton folder structure copied over to userdata partitions upon their first initialization (though some subfolders aren't). The script that handles this is at ''/etc/init.d/S12populateshare''. Includes the generated (from ''es_systems.yml'' at build time) ''info.txt'' and static (always present) ''readme.txt'' files. When a drive is initialized, these files are copied with an underscore (''_'') added before their filename to the userdata partition. | | | Skeleton directory structure | Various scripts copy files to ''data'' (formerly ''datainit'') during compilation | ''/usr/share/batocera/data/'' (formerly ''/usr/share/batocera/datainit/'') | The skeleton folder structure copied over to userdata partitions upon their first initialization (though some subfolders aren't). The script that handles this is at ''/etc/init.d/S12populateshare''. Includes the generated (from ''es_systems.yml'' at build time) ''info.txt'' and static (always present) ''readme.txt'' files. When a drive is initialized, these files are copied with an underscore (''_'') added before their filename to the userdata partition. | |
| | ROM directory bundled files | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/emulationstation/batocera-es-system/roms | ''/usr/share/batocera/datainit/roms'', which is copied to ''/userdata/roms/'' on drive initialization | These are all the bundled ROMs with their metadata/images included with a freshly-flashed Batocera install. Also includes additional readme files that weren't generated by ''es_systems.yml''. Emulators that fail to create their own directory can instead have it created here. | | | ROM directory bundled files | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/emulationstation/batocera-es-system/roms | ''/usr/share/batocera/data/roms'' (formerly ''/usr/share/batocera/datainit/roms''), which is copied to ''/userdata/roms/'' on drive initialization | These are all the bundled ROMs with their metadata/images included with a freshly-flashed Batocera install. Also includes additional readme files that weren't generated by ''es_systems.yml''. Emulators that fail to create their own directory can instead have it created here. | |
| | ES themes | Theme has its own repo, https://github.com/fabricecaruso/es-theme-carbon which is called from at https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/emulationstation/es-theme-carbon/es-theme-carbon.mk | ''/usr/share/emulationstation/themes/'', user can append more themes by adding them to ''/userdata/themes/'' | Themes included with Batocera. Right now, only es-theme-carbon is included: https://github.com/fabricecaruso/es-theme-carbon | | | ES themes | Theme has its own repo, https://github.com/fabricecaruso/es-theme-carbon which is called from at https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/emulationstation/es-theme-carbon/es-theme-carbon.mk | ''/usr/share/emulationstation/themes/'', user can append more themes by adding them to ''/userdata/themes/'' | Themes included with Batocera. Right now, only es-theme-carbon is included: https://github.com/fabricecaruso/es-theme-carbon | |
| | Downloadable themes | https://updates.batocera.org/themes.txt | The list which shows which themes can be downloaded directly from their Github repository in the Content Downloader. | | | Downloadable themes | https://batocera.org/themes.php | The list which shows which themes can be downloaded directly from their Github repository in the Content Downloader. | |
| | Batocera bezels (for RetroArch/MAME) | https://github.com/batocera-linux/batocera-bezel | ''/usr/share/batocera/datainit/decorations/default/systems/'', where ''default/'' is symlinked to ''default_unglazed/'' | The "decorations" included and displayed in-game by default. Two files are required for a bezel, the PNG image and the respective INFO text file specifying its viewport dimensions. | | | Batocera bezels (for RetroArch/MAME) | https://github.com/batocera-linux/batocera-bezel | ''/usr/share/batocera/data/decorations/default/systems/'' (formerly ''/usr/share/batocera/datainit/decorations/default/systems/''), where ''default/'' is symlinked to ''default_unglazed/'' | The "decorations" included and displayed in-game by default. Two files are required for a bezel, the PNG image and the respective INFO text file specifying its viewport dimensions. | |
| | Batocera controller overlays | https://github.com/batocera-linux/batocera-controller-overlays | ''/usr/share/batocera/controller-overlays/'' | The "system" decoration tattoos which show the current system's controls. Only one file is required for this (so far), a PNG with 225px width. | | | Batocera controller overlays | https://github.com/batocera-linux/batocera-controller-overlays | ''/usr/share/batocera/controller-overlays/'' | The "system" decoration tattoos which show the current system's controls. Only one file is required for this (so far), a PNG with 225px width. | |
| | Batocera splash screen | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core/batocera-splash | ''/usr/share/batocera/splash/'', custom splashes at ''/userdata/splash/'' | The default splash video/image used by Batocera. The user can choose to import their own splash video/image instead. | | | Batocera splash screen | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core/batocera-splash | ''/usr/share/batocera/splash/'', custom splashes at ''/userdata/splash/'' | The default splash video/image used by Batocera. The user can choose to import their own splash video/image instead. | |
| ^ File purpose ^ Github source location ^ Final image location (x86_64) ^ Notes ^ | ^ File purpose ^ Github source location ^ Final image location (x86_64) ^ Notes ^ |
| | Architecture boot makefiles/binaries | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/boot | Used in compiling Batocera; if binaries are included then ''/boot/'' | These are the makefiles for building the boot partition. Usually just a manner of copying files over from the below directory, but sometimes require a bit more complex instructions. | | | Architecture boot makefiles/binaries | https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/boot | Used in compiling Batocera; if binaries are included then ''/boot/'' | These are the makefiles for building the boot partition. Usually just a manner of copying files over from the below directory, but sometimes require a bit more complex instructions. | |
| | Boot partition patches | https://github.com/batocera-linux/batocera.linux/tree/master/board/batocera | Usually in boot, but patches can be applied to any location as needed | These are the patches made on a per-platform basis. Most of the time, they're just the simple files required to boot the system, but can also include special patches/configuration files needed to have particular components work on a particular platform. ''fsoverlay'' contains the files copied over to the boot partition. Try to keep this as small as possible, only the minimum required to boot the device, and handle the rest with packages. | | | Boot and userdata partition patches | https://github.com/batocera-linux/batocera.linux/tree/master/board/batocera | Usually in boot, but patches can be applied to any location as needed | These are the patches made on a per-platform basis. Most of the time, they're just the simple files required to boot the system, but can also include special patches/configuration files needed to have particular components work on a particular platform. ''boot'' contains the files copied over to the boot partition, while ''fsoverlay'' contains the files to be copied over to the userdata partition. Try to keep this as small as possible, only the minimum required to boot the device, and handle the rest with packages. | |
| | Build flags | https://github.com/batocera-linux/batocera.linux/tree/master/configs | N/A, only used in compiling Batocera | Boot flags, which define what components will be built with your image depending on your chose architecture. If you're trying to port Batocera to a new architecture (device, platform, new bit mode, etc.) this is the file you'll need to edit. More information on [[batocera.linux_buildroot_modifications#define_your_configuration|the build configuration section on the buildroot compiling page]]. | | | Build flags | https://github.com/batocera-linux/batocera.linux/tree/master/configs | N/A, only used in compiling Batocera | Boot flags, which define what components will be built with your image depending on your chose architecture. If you're trying to port Batocera to a new architecture (device, platform, new bit mode, etc.) this is the file you'll need to edit. More information on [[batocera.linux_buildroot_modifications#define_your_configuration|the build configuration section on the buildroot compiling page]]. | |
| | Included emulators config file | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-system/Config.in | N/A, used during compilation | This decides which emulators are included in which platform images. If your platform doesn't support a particular emulator or the system performs too poorly to be usable in any aspect, this is where you would go to disable it. | | | Included emulators config file | https://github.com/batocera-linux/batocera.linux/blob/master/package/batocera/core/batocera-system/Config.in | N/A, used during compilation | This decides which emulators are included in which platform images. If your platform doesn't support a particular emulator or the system performs too poorly to be usable in any aspect, this is where you would go to disable it. | |
| | Boot scripts | Mixture of packages from https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core and https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core/batocera-scripts/scripts | ''/etc/init.d/'' | All the init.d scripts that run at boot time. This can be helpful in diagnosing what order Batocera is initializing modules/files in. | | | Boot scripts | Mixture of packages from https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core and https://github.com/batocera-linux/batocera.linux/tree/master/package/batocera/core/batocera-scripts/scripts | ''/etc/init.d/'' | All the init.d scripts that run at boot time. This can be helpful in diagnosing what order Batocera is initializing modules/files in. | |
| |