summaryrefslogtreecommitdiff
path: root/weston.ini.in
AgeCommit message (Collapse)AuthorFilesLines
2014-08-15libinput: Add tap configuration to weston.iniJonas Ådahl1-0/+3
Enable by adding the following to your weston.ini: [libinput] enable_tap=true This also makes weston require libinput >= 0.5.0. Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
2014-06-25screen-share: Allow fullscreen shell command to be configuredAndrew Wedgbury1-0/+3
I've updated this based on comments, simplifying the command handling. Currently the screen-share module uses a hard-coded command to start the fullscreen shell server. This patch causes the module to read the command from the weston config file (from the "command" key in the "screen-share" section). The default value remains the same (i.e. to run weston with the RDP backend and fullscreen shell), but is now located in the weston config file. As well as allowing the arguments to the fullscreen shell server to be changed, this also permits an alternative fullscreen shell server to be used if required, without needing to recompile. Since the command is run as the user running weston, this should not pose any additional security risk. Signed-off-by: Andrew Wedgbury <andrew.wedgbury@realvnc.com>
2014-06-24Change the defacto output transform from flipped-270 to flipped-90Jason Ekstrand1-1/+1
It turns out that flipped-270 is the second-simplest transformation besides normal because it is a direct swapping of the x and y axes. Having that as the default encourages people to use flipped-270 as the default test for "I want to try this with a transform". Unfortunately, because flipped-270 is so simple, it is really easy to have something that works for normal, flipped-270, and nothing else. This encourages people to test with a transform thats actually "hard".
2014-06-24Fix a commentJason Ekstrand1-1/+1
2014-02-18weston.ini.in: Update path to weston-flowerJasper St. Pierre1-1/+1
Ever since the autotools flattening, the launcher for weston-flower contained an incorrect path...
2013-11-27Automatically generate weston.ini with the right pathsNeil Roberts1-0/+67
Previously weston.ini had hardcoded paths for the weston-* clients in /usr/bin and /usr/libexec. This was a bit annoying when testing Weston because you wouldn't usually install those in the system prefix. This patch adds a make rule to automatically generate weston.ini from a template file with some replacement markers for the paths so that they can have the right prefix.