keii.dev
1Linux
2================================================================================
3
4By default SDL will only link against glibc, the rest of the features will be
5enabled dynamically at runtime depending on the available features on the target
6system. So, for example if you built SDL with XRandR support and the target
7system does not have the XRandR libraries installed, it will be disabled
8at runtime, and you won't get a missing library error, at least with the
9default configuration parameters.
10
11
12Build Dependencies
13--------------------------------------------------------------------------------
14
15Ubuntu 18.04, all available features enabled:
16
17 sudo apt-get install build-essential git make \
18 pkg-config cmake ninja-build gnome-desktop-testing libasound2-dev libpulse-dev \
19 libaudio-dev libjack-dev libsndio-dev libx11-dev libxext-dev \
20 libxrandr-dev libxcursor-dev libxfixes-dev libxi-dev libxss-dev \
21 libxkbcommon-dev libdrm-dev libgbm-dev libgl1-mesa-dev libgles2-mesa-dev \
22 libegl1-mesa-dev libdbus-1-dev libibus-1.0-dev libudev-dev fcitx-libs-dev
23
24Ubuntu 22.04+ can also add `libpipewire-0.3-dev libwayland-dev libdecor-0-dev liburing-dev` to that command line.
25
26Fedora 35, all available features enabled:
27
28 sudo yum install gcc git-core make cmake \
29 alsa-lib-devel pulseaudio-libs-devel nas-devel pipewire-devel \
30 libX11-devel libXext-devel libXrandr-devel libXcursor-devel libXfixes-devel \
31 libXi-devel libXScrnSaver-devel dbus-devel ibus-devel fcitx-devel \
32 systemd-devel mesa-libGL-devel libxkbcommon-devel mesa-libGLES-devel \
33 mesa-libEGL-devel vulkan-devel wayland-devel wayland-protocols-devel \
34 libdrm-devel mesa-libgbm-devel libusb-devel libdecor-devel \
35 pipewire-jack-audio-connection-kit-devel \
36
37Fedora 39+ can also add `liburing-devel` to that command line.
38
39NOTES:
40- The sndio audio target is unavailable on Fedora (but probably not what you
41 should want to use anyhow).
42
43openSUSE Tumbleweed:
44
45 sudo zypper in libunwind-devel libusb-1_0-devel Mesa-libGL-devel libxkbcommon-devel libdrm-devel \
46 libgbm-devel pipewire-devel libpulse-devel sndio-devel Mesa-libEGL-devel
47
48Joystick does not work
49--------------------------------------------------------------------------------
50
51If you compiled or are using a version of SDL with udev support (and you should!)
52there's a few issues that may cause SDL to fail to detect your joystick. To
53debug this, start by installing the evtest utility. On Ubuntu/Debian:
54
55 sudo apt-get install evtest
56
57Then run:
58
59 sudo evtest
60
61You'll hopefully see your joystick listed along with a name like "/dev/input/eventXX"
62Now run:
63
64 cat /dev/input/event/XX
65
66If you get a permission error, you need to set a udev rule to change the mode of
67your device (see below)
68
69Also, try:
70
71 sudo udevadm info --query=all --name=input/eventXX
72
73If you see a line stating ID_INPUT_JOYSTICK=1, great, if you don't see it,
74you need to set up an udev rule to force this variable.
75
76A combined rule for the Saitek Pro Flight Rudder Pedals to fix both issues looks
77like:
78
79 SUBSYSTEM=="input", ATTRS{idProduct}=="0763", ATTRS{idVendor}=="06a3", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"
80 SUBSYSTEM=="input", ATTRS{idProduct}=="0764", ATTRS{idVendor}=="06a3", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"
81
82You can set up similar rules for your device by changing the values listed in
83idProduct and idVendor. To obtain these values, try:
84
85 sudo udevadm info -a --name=input/eventXX | grep idVendor
86 sudo udevadm info -a --name=input/eventXX | grep idProduct
87
88If multiple values come up for each of these, the one you want is the first one of each.
89
90On other systems which ship with an older udev (such as CentOS), you may need
91to set up a rule such as:
92
93 SUBSYSTEM=="input", ENV{ID_CLASS}=="joystick", ENV{ID_INPUT_JOYSTICK}="1"
94