mirrors/pipewire
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pipewire/pipewire.git synced 2025-10-29 05:40:27 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions
pipewire/spa/examples/meson.build

32 lines
1.4 KiB
Meson
Raw Normal View History

spa: Update tests and examples Keep tests in spa/tests Make spa/examples Remove some old examples
2019-01-17 09:27:41 +01:00
if sdl_dep.found()
executable('local-v4l2', 'local-v4l2.c',
spa examples: Load plugins from SPA_PLUGIN_DIR or installed path This lets them be used installed or uninstalled, like pipewire itself. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 13:19:17 +01:00
include_directories : [configinc, spa_inc],
c_args : ['-D_GNU_SOURCE'],
spa: Update tests and examples Keep tests in spa/tests Make spa/examples Remove some old examples
2019-01-17 09:27:41 +01:00
dependencies : [dl_lib, sdl_dep, pthread_lib],
Optionally install examples and tests This makes it easier to test PipeWire in its "as-installed" state, for example in an OS distribution. The .test metadata files in ${datadir}/installed-tests/${package} are a convention taken from GNOME's installed-tests initiative, allowing a generic test-runner like gnome-desktop-testing to discover and run tests in an automatic way. The installation path ${libexecdir}/installed-tests/${package} is also a convention borrowed from GNOME's installed-tests initiative. In addition to the automated tests, I've installed example executables in the same place, for manual testing. They could be separated into a different directory if desired, but they seem like they have more similarities with the automated tests than differences: both are there to test that PipeWire works correctly, and neither should be relied on for production use. Some examples are installed in deeper subdirectories to avoid name clashes. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 14:06:36 +01:00
install : installed_tests_enabled,
install_dir : join_paths(installed_tests_execdir, 'examples', 'spa'))
libcamera: disable by default Until it is at least more comon available in distros.
2020-06-04 10:41:28 +02:00
if get_option('libcamera') and libcamera_dep.found()
executable('local-libcamera', 'local-libcamera.c',
spa examples: Load plugins from SPA_PLUGIN_DIR or installed path This lets them be used installed or uninstalled, like pipewire itself. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 13:19:17 +01:00
include_directories : [configinc, spa_inc],
c_args : ['-D_GNU_SOURCE'],
libcamera: disable by default Until it is at least more comon available in distros.
2020-06-04 10:41:28 +02:00
dependencies : [dl_lib, sdl_dep, pthread_lib, libcamera_dep],
Optionally install examples and tests This makes it easier to test PipeWire in its "as-installed" state, for example in an OS distribution. The .test metadata files in ${datadir}/installed-tests/${package} are a convention taken from GNOME's installed-tests initiative, allowing a generic test-runner like gnome-desktop-testing to discover and run tests in an automatic way. The installation path ${libexecdir}/installed-tests/${package} is also a convention borrowed from GNOME's installed-tests initiative. In addition to the automated tests, I've installed example executables in the same place, for manual testing. They could be separated into a different directory if desired, but they seem like they have more similarities with the automated tests than differences: both are there to test that PipeWire works correctly, and neither should be relied on for production use. Some examples are installed in deeper subdirectories to avoid name clashes. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 14:06:36 +01:00
install : installed_tests_enabled,
install_dir : join_paths(installed_tests_execdir, 'examples', 'spa'))
libcamera: disable by default Until it is at least more comon available in distros.
2020-06-04 10:41:28 +02:00
endif
spa: Update tests and examples Keep tests in spa/tests Make spa/examples Remove some old examples
2019-01-17 09:27:41 +01:00
endif
executable('example-control', 'example-control.c',
spa examples: Load plugins from SPA_PLUGIN_DIR or installed path This lets them be used installed or uninstalled, like pipewire itself. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 13:19:17 +01:00
include_directories : [configinc, spa_inc],
c_args : ['-D_GNU_SOURCE'],
the epoll shim should only be used by the system library. All other places should use the system library to get the right fds.
2019-11-19 15:16:18 +01:00
dependencies : [dl_lib, pthread_lib, mathlib],
Optionally install examples and tests This makes it easier to test PipeWire in its "as-installed" state, for example in an OS distribution. The .test metadata files in ${datadir}/installed-tests/${package} are a convention taken from GNOME's installed-tests initiative, allowing a generic test-runner like gnome-desktop-testing to discover and run tests in an automatic way. The installation path ${libexecdir}/installed-tests/${package} is also a convention borrowed from GNOME's installed-tests initiative. In addition to the automated tests, I've installed example executables in the same place, for manual testing. They could be separated into a different directory if desired, but they seem like they have more similarities with the automated tests than differences: both are there to test that PipeWire works correctly, and neither should be relied on for production use. Some examples are installed in deeper subdirectories to avoid name clashes. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 14:06:36 +01:00
install : installed_tests_enabled,
install_dir : join_paths(installed_tests_execdir, 'examples', 'spa'))
spa: add adapter-control example to test audioadapter nodes Example executable that runs an output audioadapter using audiotestsrc as slave with an input audioadapter using alsa-pcm-sink as slave for easy testing.
2020-01-21 14:37:06 -05:00
executable('adapter-control', 'adapter-control.c',
spa examples: Load plugins from SPA_PLUGIN_DIR or installed path This lets them be used installed or uninstalled, like pipewire itself. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 13:19:17 +01:00
include_directories : [configinc, spa_inc],
c_args : ['-D_GNU_SOURCE'],
spa: add adapter-control example to test audioadapter nodes Example executable that runs an output audioadapter using audiotestsrc as slave with an input audioadapter using alsa-pcm-sink as slave for easy testing.
2020-01-21 14:37:06 -05:00
dependencies : [dl_lib, pthread_lib, mathlib],
Optionally install examples and tests This makes it easier to test PipeWire in its "as-installed" state, for example in an OS distribution. The .test metadata files in ${datadir}/installed-tests/${package} are a convention taken from GNOME's installed-tests initiative, allowing a generic test-runner like gnome-desktop-testing to discover and run tests in an automatic way. The installation path ${libexecdir}/installed-tests/${package} is also a convention borrowed from GNOME's installed-tests initiative. In addition to the automated tests, I've installed example executables in the same place, for manual testing. They could be separated into a different directory if desired, but they seem like they have more similarities with the automated tests than differences: both are there to test that PipeWire works correctly, and neither should be relied on for production use. Some examples are installed in deeper subdirectories to avoid name clashes. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 14:06:36 +01:00
install : installed_tests_enabled,
install_dir : join_paths(installed_tests_execdir, 'examples', 'spa'))
Reference in a new issue Copy permalink