You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR moves the configuration directory from ~/.emulationstation to the
standard config locations (see README). A custom location can be set with
the new --config-dir command line option.
Based on the original patches by Herdinger, but heavily edited on some places.
Copy file name to clipboardExpand all lines: README.md
+16-7Lines changed: 16 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ cmake .
29
29
make
30
30
```
31
31
32
-
- If your problem still isn't gone, the best way to report a bug is to post an issue on GitHub. Try to post the simplest steps possible to reproduce the bug. Include files you think might be related (except for ROMs, of course). If you haven't re-run ES since the crash, the log file `~/.emulationstation/es_log.txt` is also helpful.
32
+
- If your problem still isn't gone, the best way to report a bug is to post an issue on GitHub. Try to post the simplest steps possible to reproduce the bug. Include files you think might be related (except for ROMs, of course). If you haven't re-run ES since the crash, the log file `$CONFIG_DIR/es_log.txt` is also helpful.
33
33
34
34
Building
35
35
========
@@ -79,12 +79,21 @@ Complete Raspberry Pi build instructions at [emulationstation.org](http://emulat
79
79
Configuring
80
80
===========
81
81
82
-
**~/.emulationstation/es_systems.cfg:**
83
-
When first run, an example systems configuration file will be created at `~/.emulationstation/es_systems.cfg`. `~` is `$HOME` on Linux, and `%HOMEPATH%` on Windows. This example has some comments explaining how to write the configuration file. See the "Writing an es_systems.cfg" section for more information.
82
+
Configuration files are stored in `$CONFIG_DIR`, which is by default
83
+
84
+
- on Windows: `My Documents/EmulationStation/`
85
+
- on Linux: `$XDG_CONFIG_HOME/emulationstation/` which usually defaults to `~/.config/emulationstation/`
86
+
- on OSX: `~/Library/Application Support/org.emulationstation.EmulationStation/` by default, or the same as Linux if EmulationStation is build with the `XDG_ON_OSX` CMake flag.
87
+
88
+
Alternatively you can specify `$CONFIG_DIR` through the `--config-dir [path]` command line option.
89
+
90
+
**es_systems.cfg:**
91
+
92
+
When first run, an example systems configuration file will be created at `$CONFIG_DIR/es_systems.cfg`. This example has some comments explaining how to write the configuration file. See the "Writing an es_systems.cfg" section for more information.
84
93
85
94
**Keep in mind you'll have to set up your emulator separately from EmulationStation!**
86
95
87
-
**~/.emulationstation/es_input.cfg:**
96
+
**es_input.cfg:**
88
97
When you first start EmulationStation, you will be prompted to configure an input device. The process is thus:
89
98
90
99
1. Hold a button on the device you want to configure. This includes the keyboard.
@@ -95,11 +104,11 @@ When you first start EmulationStation, you will be prompted to configure an inpu
95
104
96
105
4. Choose "SAVE" to save this device and close the input configuration screen.
97
106
98
-
The new configuration will be added to the `~/.emulationstation/es_input.cfg` file.
107
+
The new configuration will be added to the `es_input.cfg` file.
99
108
100
109
**Both new and old devices can be (re)configured at any time by pressing the Start button and choosing "CONFIGURE INPUT".** From here, you may unplug the device you used to open the menu and plug in a new one, if necessary. New devices will be appended to the existing input configuration file, so your old devices will remain configured.
101
110
102
-
**If your controller stops working, you can delete the `~/.emulationstation/es_input.cfg` file to make the input configuration screen re-appear on next run.**
111
+
**If your controller stops working, you can delete the `es_input.cfg` file to make the input configuration screen re-appear on next run.**
103
112
104
113
105
114
You can use `--help` or `-h` to view a list of command-line options. Briefly outlined here:
@@ -126,7 +135,7 @@ Complete configuration instructions at [emulationstation.org](http://emulationst
126
135
The `es_systems.cfg` file contains the system configuration data for EmulationStation, written in XML. This tells EmulationStation what systems you have, what platform they correspond to (for scraping), and where the games are located.
127
136
128
137
ES will check two places for an es_systems.cfg file, in the following order, stopping after it finds one that works:
129
-
*`~/.emulationstation/es_systems.cfg`
138
+
*`$CONFIG_DIR/es_systems.cfg`
130
139
*`/etc/emulationstation/es_systems.cfg`
131
140
132
141
The order EmulationStation displays systems reflects the order you define them in.
0 commit comments