summaryrefslogtreecommitdiff
path: root/README.wayland
diff options
context:
space:
mode:
authorChris Michael <cp.michael@samsung.com>2014-08-22 10:28:50 -0400
committerChris Michael <cp.michael@samsung.com>2014-08-22 10:28:50 -0400
commit5494ada630b166d860fdeb71dc9eff2c2e0327af (patch)
tree837e0a4137127519f6ee65c6fcbfe83b25beaa56 /README.wayland
parent462d79e14787a3365ffbfb50a859fd02d0e733ce (diff)
update README.wayland with some notes & fixes
Signed-off-by: Chris Michael <cp.michael@samsung.com>
Diffstat (limited to 'README.wayland')
-rw-r--r--README.wayland35
1 files changed, 24 insertions, 11 deletions
diff --git a/README.wayland b/README.wayland
index 8ab544637..b33848514 100644
--- a/README.wayland
+++ b/README.wayland
@@ -20,6 +20,7 @@ Firstly, you MUST have EFL built with the following options:
20 20
21 --enable-drm 21 --enable-drm
22 --enable-wayland 22 --enable-wayland
23 --enable-systemd
23 24
24This Readme does not address the dependencies needed to enable Wayland 25This Readme does not address the dependencies needed to enable Wayland
25in EFL. If you require any information for that, please see: 26in EFL. If you require any information for that, please see:
@@ -34,6 +35,17 @@ If you would like support for EGL in Wayland, then also build EFL with:
34The above options can be enabled for EFL without any adverse effects to 35The above options can be enabled for EFL without any adverse effects to
35existing applications. 36existing applications.
36 37
38Wayland-Only:
39-------------
40
41If you wish to test out the Highly Experimental standalone
42Wayland-Only (no X11) compositor, then you should checkout the
43e_comp_wl development branch:
44
45https://git.enlightenment.org/core/enlightenment.git/log/?h=devs/devilhorns/e_comp_wl
46
47Compiling:
48-------------
37 49
38Next, you will need to adjust the options that you pass to 50Next, you will need to adjust the options that you pass to
39Enlightenment during the compile phase. 51Enlightenment during the compile phase.
@@ -51,13 +63,18 @@ In order for Enlightenment to be compiled without X11, using Wayland
51only, you will need to pass a few more options to the configure stage 63only, you will need to pass a few more options to the configure stage
52of Enlightenment: 64of Enlightenment:
53 65
54 --enable-wayland-only
55 --enable-wayland-clients 66 --enable-wayland-clients
56 --enable-wl-drm 67 --enable-wl-drm
57 68
69If you wish to test the experimental Wayland-Only compositor, then
70also pass to configure:
71
72 --enable-wayland-only
73
58Since this is all still a work-in-progress, there are a few 74Since this is all still a work-in-progress, there are a few
59Enlightenment modules that have not been "fixed" to work without X11 75Enlightenment modules that have not been "fixed" to work without X11
60yet. Those will need to be disabled: 76yet. Those will need to be disabled if you enabled the wayland-only
77option:
61 78
62 --disable-shot 79 --disable-shot
63 --disable-xkbswitch 80 --disable-xkbswitch
@@ -84,7 +101,8 @@ In order for Enlightenment to function without X11, we need to setup
84the environment. In your current tty, do: 101the environment. In your current tty, do:
85 102
86 export E_WL_FORCE=drm 103 export E_WL_FORCE=drm
87 export ELM_ENGINE=wayland_shm (or wayland_egl) 104 export ELM_DISPLAY=wl
105 export ELM_ACCEL=opengl (or 'none' for SHM engine)
88 106
89This will make sure that Enlightenment renders using DRM, and any 107This will make sure that Enlightenment renders using DRM, and any
90Elementary applications use a Wayland engine. 108Elementary applications use a Wayland engine.
@@ -121,14 +139,9 @@ Bugs:
121 139
122Yes, there are Lots of them !! 140Yes, there are Lots of them !!
123Yes, I am already aware of 99.9% of them. 141Yes, I am already aware of 99.9% of them.
124No, you do not need to start reporting them yet !! 142Yes, you can start reporting them ... if you do create tickets for
143any bugs, please note in your ticket that you are using the e_comp_wl
144branch.
125 145
126When we feel that the work is reaching a "finalizing" stage, we will 146When we feel that the work is reaching a "finalizing" stage, we will
127put out a request for actual testers and bug reports ! 147put out a request for actual testers and bug reports !
128
129You are here because you want to play...because you want to
130experiment...because you want to be "cool" ;) You are not hear to nag
131me with complaints & reports about things I am already well aware of
132;) Save yourself some time, and me some stress !! ;)
133
134