mirrors/weston
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
3097acc702
weston/pipewire/meson.build

31 lines
860 B
Meson
Raw Normal View History

Add pipewire plugin It is quite similar to the remoting plugin. It just exports the frames via pipewire instead of the builtin GStreamer pipeline. It implements the same virtual output API. Virtual outputs can be created by adding 'pipewire-output' sections to weston.ini. The generated frames can be accessed with any pipewire client. e.g. with GStreamer: gst-launch-1.0 pipewiresrc ! video/x-raw,format=BGRx ! ... Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
2019-04-23 13:34:05 +03:00
if get_option('pipewire')
user_hint = 'If you rather not build this, set "pipewire=false".'
if not get_option('backend-drm')
error('Attempting to build the pipewire plugin without the required DRM backend. ' + user_hint)
endif
depnames = [
'libpipewire-0.2', 'libspa-0.1'
]
build: separate deps for int and ext libweston users We have two kinds of libweston users: internal and external. Weston, the frontend, counts as an external user, and should not have access to libweston private headers. The shell plugins are external users as well, because we intend people to be able to write them. Renderers, backends, and some plugins are internal users who will need access to private headers. Create two different Meson dependency objects, one for each kind. This makes it less likely to accidentally use a private header. Screen-share is a Weston plugin and therefore counts as an external user, but it needs the backend API to deliver input. Until we are comfortable exposing public API for that purpose, let it use internal headers. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-04-18 16:43:55 +03:00
deps_pipewire = [ dep_libweston_private ]
Add pipewire plugin It is quite similar to the remoting plugin. It just exports the frames via pipewire instead of the builtin GStreamer pipeline. It implements the same virtual output API. Virtual outputs can be created by adding 'pipewire-output' sections to weston.ini. The generated frames can be accessed with any pipewire client. e.g. with GStreamer: gst-launch-1.0 pipewiresrc ! video/x-raw,format=BGRx ! ... Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
2019-04-23 13:34:05 +03:00
foreach depname : depnames
dep = dependency(depname, required: false)
if not dep.found()
error('Pipewire plugin requires @0@ which was not found. '.format(depname) + user_hint)
endif
deps_pipewire += dep
endforeach
plugin_pipewire = shared_library(
'pipewire-plugin',
'pipewire-plugin.c',
build: simplify include_directories Define common_inc which includes both public_inc and the project root directory. The project root directory will allow access to config.h and all the shared/ headers. Replacing all custom '.', '..', '../..', '../shared' etc. include paths with common_inc reduces clutter in the target definitions and enforces the common #include directive style, as e.g. including shared/ headers without the subdirectory name no longer works. Unfortunately this does not prevent one from using private libweston headers with the usual include pattern for public headers. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-04-05 17:09:28 +03:00
include_directories: common_inc,
Add pipewire plugin It is quite similar to the remoting plugin. It just exports the frames via pipewire instead of the builtin GStreamer pipeline. It implements the same virtual output API. Virtual outputs can be created by adding 'pipewire-output' sections to weston.ini. The generated frames can be accessed with any pipewire client. e.g. with GStreamer: gst-launch-1.0 pipewiresrc ! video/x-raw,format=BGRx ! ... Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
2019-04-23 13:34:05 +03:00
dependencies: deps_pipewire,
name_prefix: '',
install: true,
install_dir: dir_module_libweston
)
env_modmap += 'pipewire-plugin.so=@0@;'.format(plugin_pipewire.full_path())
endif
Reference in New Issue Copy Permalink