weston

History

Pekka Paalanen 3728d7e99b backend-drm,pipewire,remoting: do not set monitor serial to "unknown" If serial is unknown, it's best to leave it as NULL. All usage sites already deal with it possibly being NULL. This makes DRM-backend consistent with all other backend that leave serial as NULL, allowing to move the initialization of these fields into core. Pipewire and remoting plugins are modified just for consistency. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>		2023-09-15 06:56:59 +00:00
..
meson.build	plug-ins: Migrate pipewire and remoting plug-ins headers to public header	2020-09-04 10:36:48 +00:00
README	doc: Move helper scripts to doc/scripts	2019-06-25 14:05:54 +00:00
remoting-plugin.c	backend-drm,pipewire,remoting: do not set monitor serial to "unknown"	2023-09-15 06:56:59 +00:00

README

	Remoting plugin for Weston


The Remoting plugin creates a streaming image of a virtual output and transmits
it to a remote host. It is currently only supported on the drm-backend. Virtual
outputs are created and configured by adding a remote-output section to
weston.ini. See man weston-drm(7) for configuration details. This plugin is
loaded automatically if any remote-output sections are present.

This plugin sends motion jpeg images to a client via RTP using gstreamer, and
so requires gstreamer-1.0. This plugin starts sending images immediately when
weston is run, and keeps sending them until weston shuts down. The image stream
can be received by any appropriately configured RTP client, but a sample
gstreamer RTP client script can be found at doc/scripts/remoting-client-receive.bash.

Script usage:
	remoting-client-receive.bash <PORT NUMBER>


How to compile
---------------
Set --enable-remoting=true when configuring weston. The remoting-plugin.so
module is created and installed in the libweston path.


How to configure weston.ini
----------------------------
See man weston-drm(7).