Add swaylock protocol, add resource destructors

This prevents sway crashing if swaybg or swaybar dies.

3 files changed, 29 insertions, 0 deletions

diff --git a/protocols/CMakeLists.txt b/protocols/CMakeLists.txt
index 07becc36..d7516d0c 100644
--- a/protocols/CMakeLists.txt
+++ b/protocols/CMakeLists.txt
@@ -13,10 +13,21 @@ WAYLAND_ADD_PROTOCOL_SERVER(proto-server-desktop-shell
         desktop-shell
 )
 
+WAYLAND_ADD_PROTOCOL_CLIENT(proto-client-swaylock
+        swaylock.xml
+        swaylock
+)
+WAYLAND_ADD_PROTOCOL_SERVER(proto-server-swaylock
+        swaylock.xml
+        swaylock
+)
+
 add_library(sway-protocols
         ${proto-client-xdg-shell}
         ${proto-client-desktop-shell}
         ${proto-server-desktop-shell}
+        ${proto-client-swaylock}
+        ${proto-server-swaylock}
         )
 
 set(PROTOCOLS_INCLUDE_DIRS ${CMAKE_BINARY_DIR}/protocols PARENT_SCOPE)
diff --git a/protocols/libsway-protocols.a b/protocols/libsway-protocols.a
new file mode 100644
index 00000000..284f46c2
--- /dev/null
+++ b/protocols/libsway-protocols.a
diff --git a/protocols/swaylock.xml b/protocols/swaylock.xml
new file mode 100644
index 00000000..c7a102dd
--- /dev/null
+++ b/protocols/swaylock.xml
@@ -0,0 +1,18 @@
+<protocol name="lock">
+
+  <interface name="lock" version="1">
+    <description summary="create lock screen UIs">
+      The Weston desktop-shell protocol's locking functionality depends more
+      on the behavior of the compositor than of a screen locking client, so
+      another protocol is necessary.
+    </description>
+
+    <request name="set_lock_surface">
+      <arg name="output" type="object" interface="wl_output"/>
+      <arg name="surface" type="object" interface="wl_surface"/>
+    </request>
+
+    <request name="unlock"/>
+
+  </interface>
+</protocol>