pipewire/spa/plugins/v4l2/meson.build

v4l2_sources = ['v4l2.c',
                'v4l2-device.c',
                'v4l2-source.c']
v4l2_dependencies = [ spa_dep, libinotify_dep, mathlib ]

if libudev_dep.found()
  v4l2_sources += [ 'v4l2-udev.c' ]
  v4l2_dependencies += [ libudev_dep ]
  if logind_dep.found()
    v4l2_dependencies += [ logind_dep ]
  endif
endif

v4l2lib = shared_library('spa-v4l2',
                          v4l2_sources,
                          include_directories : [ configinc ],
                          dependencies : v4l2_dependencies,
                          install : true,
                          install_dir : spa_plugindir / 'v4l2')
video: add video format start working on v4l2 source 2016-07-05 17:58:34 +02:00			`v4l2_sources = ['v4l2.c',`
device: add device object Make a device object, let the v4l2 monitor create device objects The device object is responsible for dynamically creating nodes. 2018-11-23 12:43:47 +01:00			`'v4l2-device.c',`
video: add video format start working on v4l2 source 2016-07-05 17:58:34 +02:00			`'v4l2-source.c']`
v4l2: use dll to track rate difference Track the difference between the configured and real framerate and use that as the rate correction to adjust the next_nsec clock field. 2024-11-26 17:14:26 +01:00			`v4l2_dependencies = [ spa_dep, libinotify_dep, mathlib ]`
meson: fix build with missing libudev-devel 2024-01-26 13:28:07 +01:00
			`if libudev_dep.found()`
spa: v4l2: Use systemd-logind to listen for access changes There is a race between logind applying ACLs to allow the active session of a locally present user access to devices with a udev uaccess tag (like /dev/video# nodes) getting applied vs wireplumber/pipewire starting. Wireplumber/pipewire are part of the (user) default.target, which gets started as soon as a user logs in and systemd --user is started for that user, where as logind only starts applying the ACLs after the gnome-shell associated logind session has been created. This race may cause pipewire to not see v4l2 video sources at login, this can be reproduced with these steps: 1. sudo setfacl --remove-all /dev/video* 2. systemctl --user restart pipewire 3. Now wp-ctl status will not show any video devices (like if pipewire was started before the udev uaccess ACLs got applied) 4. Do a switch to another (test) user without logging out, e.g. in GNOME go to the top right system menu press the power on/off icon and select "Switch User..." 5. Switch back to your normal user. Run getfacl /dev/video0 this will show your user has access now. 6. wp-ctl status should show the camera now, but it does not. Fix pipewire not seeing v4l2 sources in this case by making v4l2-udev monitor systemd-logind session changes and redoing the access() checks on /dev/video# nodes when the session changes. Closes: #3539 Closes: #3960 Signed-off-by: Hans de Goede <hdegoede@redhat.com> 2024-09-10 11:14:35 +02:00			`v4l2_sources += [ 'v4l2-udev.c' ]`
			`v4l2_dependencies += [ libudev_dep ]`
spa: use a separate logind dependency separate from systemd non-systemd systems also have logind, in the form of elogind, which works to resolve the v4l2 video source race just as well. permit finding elogind, by using a separate dep object. 2024-09-20 03:12:04 +02:00			`if logind_dep.found()`
			`v4l2_dependencies += [ logind_dep ]`
spa: v4l2: Use systemd-logind to listen for access changes There is a race between logind applying ACLs to allow the active session of a locally present user access to devices with a udev uaccess tag (like /dev/video# nodes) getting applied vs wireplumber/pipewire starting. Wireplumber/pipewire are part of the (user) default.target, which gets started as soon as a user logs in and systemd --user is started for that user, where as logind only starts applying the ACLs after the gnome-shell associated logind session has been created. This race may cause pipewire to not see v4l2 video sources at login, this can be reproduced with these steps: 1. sudo setfacl --remove-all /dev/video* 2. systemctl --user restart pipewire 3. Now wp-ctl status will not show any video devices (like if pipewire was started before the udev uaccess ACLs got applied) 4. Do a switch to another (test) user without logging out, e.g. in GNOME go to the top right system menu press the power on/off icon and select "Switch User..." 5. Switch back to your normal user. Run getfacl /dev/video0 this will show your user has access now. 6. wp-ctl status should show the camera now, but it does not. Fix pipewire not seeing v4l2 sources in this case by making v4l2-udev monitor systemd-logind session changes and redoing the access() checks on /dev/video# nodes when the session changes. Closes: #3539 Closes: #3960 Signed-off-by: Hans de Goede <hdegoede@redhat.com> 2024-09-10 11:14:35 +02:00			`endif`
meson: fix build with missing libudev-devel 2024-01-26 13:28:07 +01:00			`endif`
video: add video format start working on v4l2 source 2016-07-05 17:58:34 +02:00
			`v4l2lib = shared_library('spa-v4l2',`
			`v4l2_sources,`
v4l2: include config.h to check for udev 2024-02-06 22:41:54 +01:00			`include_directories : [ configinc ],`
meson: fix build with missing libudev-devel 2024-01-26 13:28:07 +01:00			`dependencies : v4l2_dependencies,`
port to meson 2016-09-26 12:15:52 +02:00			`install : true,`
spa: fix the indentation in the various meson.build files Was all over the place using tabs and spaces, let's make this more consistent. 2021-09-20 08:59:10 +10:00			`install_dir : spa_plugindir / 'v4l2')`