README-linux.md (3718B)
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 Xinerama support and the target 7system does not have the Xinerama 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 12================================================================================ 13Build Dependencies 14================================================================================ 15 16Ubuntu 13.04, all available features enabled: 17 18sudo apt-get install build-essential mercurial make cmake autoconf automake \ 19libtool libasound2-dev libpulse-dev libaudio-dev libx11-dev libxext-dev \ 20libxrandr-dev libxcursor-dev libxi-dev libxinerama-dev libxxf86vm-dev \ 21libxss-dev libgl1-mesa-dev libesd0-dev libdbus-1-dev libudev-dev \ 22libgles1-mesa-dev libgles2-mesa-dev libegl1-mesa-dev libibus-1.0-dev \ 23fcitx-libs-dev libsamplerate0-dev libsndio-dev 24 25Ubuntu 16.04+ can also add "libwayland-dev libxkbcommon-dev wayland-protocols" 26to that command line for Wayland support. 27 28NOTES: 29- This includes all the audio targets except arts, because Ubuntu pulled the 30 artsc0-dev package, but in theory SDL still supports it. 31- libsamplerate0-dev lets SDL optionally link to libresamplerate at runtime 32 for higher-quality audio resampling. SDL will work without it if the library 33 is missing, so it's safe to build in support even if the end user doesn't 34 have this library installed. 35- DirectFB isn't included because the configure script (currently) fails to find 36 it at all. You can do "sudo apt-get install libdirectfb-dev" and fix the 37 configure script to include DirectFB support. Send patches. :) 38 39 40================================================================================ 41Joystick does not work 42================================================================================ 43 44If you compiled or are using a version of SDL with udev support (and you should!) 45there's a few issues that may cause SDL to fail to detect your joystick. To 46debug this, start by installing the evtest utility. On Ubuntu/Debian: 47 48 sudo apt-get install evtest 49 50Then run: 51 52 sudo evtest 53 54You'll hopefully see your joystick listed along with a name like "/dev/input/eventXX" 55Now run: 56 57 cat /dev/input/event/XX 58 59If you get a permission error, you need to set a udev rule to change the mode of 60your device (see below) 61 62Also, try: 63 64 sudo udevadm info --query=all --name=input/eventXX 65 66If you see a line stating ID_INPUT_JOYSTICK=1, great, if you don't see it, 67you need to set up an udev rule to force this variable. 68 69A combined rule for the Saitek Pro Flight Rudder Pedals to fix both issues looks 70like: 71 72 SUBSYSTEM=="input", ATTRS{idProduct}=="0763", ATTRS{idVendor}=="06a3", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1" 73 SUBSYSTEM=="input", ATTRS{idProduct}=="0764", ATTRS{idVendor}=="06a3", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1" 74 75You can set up similar rules for your device by changing the values listed in 76idProduct and idVendor. To obtain these values, try: 77 78 sudo udevadm info -a --name=input/eventXX | grep idVendor 79 sudo udevadm info -a --name=input/eventXX | grep idProduct 80 81If multiple values come up for each of these, the one you want is the first one of each. 82 83On other systems which ship with an older udev (such as CentOS), you may need 84to set up a rule such as: 85 86 SUBSYSTEM=="input", ENV{ID_CLASS}=="joystick", ENV{ID_INPUT_JOYSTICK}="1" 87