README-linux.txt
author David Ludwig <dludwig@pobox.com>
Wed, 25 Dec 2013 21:39:48 -0500
changeset 8563 c0e68f3b6bbb
parent 7980 3122e7af0bf5
child 8784 605c4b0ef03d
permissions -rw-r--r--
WinRT: compiled the d3d11 renderer's shaders into SDL itself

Previously, the shaders would get compiled separately, the output of which would need to be packaged into the app. This change should make SDL's dll be the only binary needed to include SDL in a WinRT app.
gabomdq@7972
     1
================================================================================
gabomdq@7972
     2
Simple DirectMedia Layer for Linux
gabomdq@7972
     3
================================================================================
gabomdq@7972
     4
gabomdq@7972
     5
By default SDL will only link against glibc, the rest of the features will be
gabomdq@7972
     6
enabled dynamically at runtime depending on the available features on the target
gabomdq@7972
     7
system. So, for example if you built SDL with Xinerama support and the target
gabomdq@7972
     8
system does not have the Xinerama libraries installed, it will be disabled
gabomdq@7972
     9
at runtime, and you won't get a missing library error, at least with the 
gabomdq@7972
    10
default configuration parameters.
gabomdq@7972
    11
gabomdq@7972
    12
gabomdq@7972
    13
================================================================================
gabomdq@7972
    14
Build Dependencies
gabomdq@7972
    15
================================================================================
gabomdq@7972
    16
    
gabomdq@7972
    17
Ubuntu 13.04, all available features enabled:
gabomdq@7972
    18
gabomdq@7972
    19
sudo apt-get install build-essential mercurial make cmake autoconf automake \
gabomdq@7972
    20
libtool libasound2-dev libpulse-dev libaudio-dev libx11-dev libxext-dev \
gabomdq@7972
    21
libxrandr-dev libxcursor-dev libxi-dev libxinerama-dev libxxf86vm-dev \
gabomdq@7972
    22
libxss-dev libgl1-mesa-dev libesd0-dev libdbus-1-dev libudev-dev \
gabomdq@7972
    23
libgles1-mesa-dev libgles2-mesa-dev libegl1-mesa-dev
gabomdq@7972
    24
gabomdq@7973
    25
NOTES:
gabomdq@7973
    26
- This includes all the audio targets except arts, because Ubuntu pulled the 
gabomdq@7973
    27
  artsc0-dev package, but in theory SDL still supports it.
gabomdq@7973
    28
- DirectFB isn't included because the configure script (currently) fails to find
gabomdq@7973
    29
  it at all. You can do "sudo apt-get install libdirectfb-dev" and fix the 
gabomdq@7973
    30
  configure script to include DirectFB support. Send patches.  :)
gabomdq@7972
    31
gabomdq@7973
    32
gabomdq@7980
    33
================================================================================
gabomdq@7980
    34
Joystick does not work
gabomdq@7980
    35
================================================================================
gabomdq@7980
    36
gabomdq@7980
    37
If you compiled or are using a version of SDL with udev support (and you should!)
gabomdq@7980
    38
there's a few issues that may cause SDL to fail to detect your joystick. To
gabomdq@7980
    39
debug this, start by installing the evtest utility. On Ubuntu/Debian:
gabomdq@7980
    40
gabomdq@7980
    41
    sudo apt-get install evtest
gabomdq@7980
    42
    
gabomdq@7980
    43
Then run:
gabomdq@7980
    44
    
gabomdq@7980
    45
    sudo evtest
gabomdq@7980
    46
    
gabomdq@7980
    47
You'll hopefully see your joystick listed along with a name like "/dev/input/eventXX"
gabomdq@7980
    48
Now run:
gabomdq@7980
    49
    
gabomdq@7980
    50
    cat /dev/input/event/XX
gabomdq@7980
    51
gabomdq@7980
    52
If you get a permission error, you need to set a udev rule to change the mode of
gabomdq@7980
    53
your device (see below)    
gabomdq@7980
    54
    
gabomdq@7980
    55
Also, try:
gabomdq@7980
    56
    
gabomdq@7980
    57
    sudo udevadm info --query=all --name=input/eventXX
gabomdq@7980
    58
    
gabomdq@7980
    59
If you see a line stating ID_INPUT_JOYSTICK=1, great, if you don't see it,
gabomdq@7980
    60
you need to set up an udev rule to force this variable.
gabomdq@7980
    61
gabomdq@7980
    62
A combined rule for the Saitek Pro Flight Rudder Pedals to fix both issues looks 
gabomdq@7980
    63
like:
gabomdq@7980
    64
    
gabomdq@7980
    65
   SUBSYSTEM=="input", ATTRS{idProduct}=="0763", ATTRS{idVendor}=="06a3", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"
gabomdq@7980
    66
   SUBSYSTEM=="input", ATTRS{idProduct}=="0764", ATTRS{idVendor}=="06a3", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"
gabomdq@7980
    67
   
gabomdq@7980
    68
You can set up similar rules for your device by changing the values listed in
gabomdq@7980
    69
idProduct and idVendor. To obtain these values, try:
gabomdq@7980
    70
    
gabomdq@7980
    71
    sudo udevadm info -a --name=input/eventXX | grep idVendor
gabomdq@7980
    72
    sudo udevadm info -a --name=input/eventXX | grep idProduct
gabomdq@7980
    73
    
gabomdq@7980
    74
If multiple values come up for each of these, the one you want is the first one of each.    
gabomdq@7980
    75
gabomdq@7980
    76
On other systems which ship with an older udev (such as CentOS), you may need
gabomdq@7980
    77
to set up a rule such as:
gabomdq@7980
    78
    
gabomdq@7980
    79
    SUBSYSTEM=="input", ENV{ID_CLASS}=="joystick", ENV{ID_INPUT_JOYSTICK}="1"
gabomdq@7980
    80