This is a bugfix upgrade with some necessary changes to the recipe itself.
Changelogs:
https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.23https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.24
Fixes in the recipe itself:
- meson_options.txt now uses features for everything, so the
"=true" and "=false" packageconfig args were replaced by
"=enabled" and "=disabled", respectively
- "docs" packageconfig was incorrectly adding doxygen instead
of doxygen-native to the DEPENDS variable
- "man" packageconfig removed, since manpage generation requires
xmltoman, and that tool is not available
Signed-off-by: Carlos Rafael Giani <crg7475@mailbox.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* Use a versioned recipe instead of _git
* Add more packageconfigs: alsa, docs, sdl2, sndfile, v4l2,
pipewire-alsa, pipewire-jack
* Split SPA and module packages dynamically to generate one package for
each SPA plugin and for each module
* Split pipewire library, shim PulseAudio daemon, main tools & SPA tools,
pipewire-alsa, pipewire-jack, ALSA card profiles, GStreamer plugin,
and example session manager into separate packages
* Set up a "pipewire" user and group to run the PipeWire daemon with that
user instead of root
Signed-off-by: Carlos Rafael Giani <crg7475@mailbox.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Drop the gcc10 patches the problem is fixed in newer versions
Migrate to use meson build system
Drop libwrap packageconfig, its dropped upstream too
Use systemd_user_unit_dir to match OE
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Max Kellermann <max.kellermann@gmail.com>
Cc: Andreas Müller <schnitzeltony@gmail.com>
Latest perl have switched the default to not allow the unsafe include
paths like current dir (.), but dvb-apps depend on this behaviour
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Andreas Müller <schnitzeltony@gmail.com>
Some older arm32 cores are without neon units e.g. armv6 (rpi0 fame)
therefore check for neon feature before enabling it
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Andreas Müller <schnitzeltony@gmail.com>
* a regression introduced in 2.1.0 prevented chorus from being audible when fluid_synth_process() was used (#751, thanks to @chirs241097)
* a regression introduced in 2.0.6 prevented the MIDI player from restarting playback after all files have been played (#755, thanks to @rncbc)
* fix a double-free violation introduced in 2.0.0 after executing the info shell command (#756)
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
since libsrtp does not run automake, it does not get to add missing
files e.g. ar-lib macro file which is needed during autoreconf,
therefore copy this file from native automake to use here
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Andreas Müller <schnitzeltony@gmail.com>
Release notes:
SoundFonts may never be unloaded correctly, if
polyphony is ever exceeded (#727), or
voices are still playing while their SoundFont is being unloaded.
Calling delete_fluid_synth() does not free those SoundFonts either. Affected are versions from 1.1.4 to 2.1.5 .
Other bug-fixes:
fix a heap-based use-after-free (#733)
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Secure Reliable Transport (SRT) Protocol
Secure Reliable Transport (SRT) is an open source transport technology that
optimizes streaming performance across unpredictable networks, such as the Internet.
SRT is applied to contribution and distribution endpoints as part of a video
stream workflow to deliver the best quality and lowest latency video at all times.
As audio/video packets are streamed from a source to a destination device,
SRT detects and adapts to the real-time network conditions between the two endpoints.
SRT helps compensate for jitter and bandwidth fluctuations due to congestion
over noisy networks, such as the Internet. Its error recovery mechanism minimizes
the packet loss typical of Internet connections. And SRT supports AES encryption for
end-to-end security, keeping your streams safe from prying eyes.
* 0001-don-t-install-srt-ffplay.patch
Upstream-Status: Pending
Signed-off-by: Jose Quaresma <quaresma.jose@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* resolves bitbake world error:
ERROR: Nothing PROVIDES 'ffmpeg' (but meta-multimedia/recipes-multimedia/musicpd/mpd_0.20.22.bb DEPENDS on or otherwise requires it)
ffmpeg was skipped: because it has a restricted license 'commercial'. Which is not whitelisted in LICENSE_FLAGS_WHITELIST
ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'mpd', 'ffmpeg']
* aac is conditionally included in PACKAGECONFIG based on LICENSE_FLAGS
since:
commit f5d271fd54
Author: Armin Kuster <akuster808@gmail.com>
Date: Mon Oct 1 08:05:28 2018 -0700
mpd: enable aac PACKAGECONFIG only with commercial LICENSE_FLAGS
maybe we could use the same for ffmpeg, but the conditional should
be a bit more complicated, because the aac support is whitelisted by
either commercial, commercial_faad2 or faad2 in LICENSE_FLAGS_WHITELIST
not just currently checked 'commercial'.
and we cannot use LICENSE_FLAGS conditional in both, because that leads to
bb.data_smart.ExpansionError: Failure expanding variable LICENSE_FLAGS, expression was
${@bb.utils.contains('PACKAGECONFIG', 'ffmpeg', 'commercial', '', d)}
which triggered exception RecursionError: maximum recursion depth exceeded
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
ERROR: Nothing RPROVIDES 'fdk-aac' (but meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb RDEPENDS on or otherwise requires it)
fdk-aac was skipped: because it has a restricted license 'commercial'. Which is not whitelisted in LICENSE_FLAGS_WHITELIST
NOTE: Runtime target 'fdk-aac' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['fdk-aac']
ERROR: Nothing RPROVIDES 'mpd' (but meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb RDEPENDS on or otherwise requires it)
mpd was skipped: because it has a restricted license 'commercial'. Which is not whitelisted in LICENSE_FLAGS_WHITELIST
NOTE: Runtime target 'mpd' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['mpd']
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
fluidsynth 2.1.5:
* loading DLS may have failed in certain setup environments (#666)
* fix a build failure with GCC 4.8 (#661, thanks to @ffontaine)
fluidsynth 2.1.4:
* fix an uninitialized memory access possibly triggering an FPE trap
* fix several regressions introduced in 2.1.3:
fluid_synth_start() failed for certain presets
fix a NULL dereference in jack driver
fix a stack-based overflow when creating the synth
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Fix incorrect links and replace the defunct "gitorious" with now popular
"GitLab".
Signed-off-by: Diego Rondini <diego.rondini@kynetics.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Bumped to latest source revision of libcamera, and added packageconfig
to enable the gstreamer during build, and to generate and install the
gstreamer library.
Signed-off-by: Madhavan Krishnan <madhavan.krishnan@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
It ends up with textrels otherwise
QA Issue: gerbera: ELF binary /usr/bin/gerbera has relocations in .text
[textrel]
Signed-off-by: Khem Raj <raj.khem@gmail.com>
libcamera checks if RPATH or RUNPATH dynamic tag is present in
libcamera.so. If it does, it assumes that libcamera binaries are
run directly from the build directory without installing them, and
tries to use resorces like IPA modules from the build directory.
Mainline meson strips RPATH/RUNPATH out from libcamera.so file
at install time. But openembedded-core patches meson to disable
RPATH/RUNPATH removal. That's why we need to remove this tag manually
in do_install_append().
IPA module is signed (with openssl dgst) after it is built. But
during packaging the OE build system 1) splits out debugging info,
and 2) strips the binaries. So the IPA module so file installed
isn't the one which the signature was calculated against. Then
the signature check fails, and libcamera tries to run the IPA
module isolated (in a sandbox), which doesn't work if the IPA
module wasn't designed to run isolated. The solution is to
recalculate the IPA modules signatures in ${PKGD} after do_package().
Signed-off-by: Andrey Konovalov <andrey.konovalov@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Khem Raj
Martin Jansa
Oleksandr Kravchuk
Carlos Rafael Giani
Andreas Müller
Diego Santa Cruz
Jose Quaresma
Lim Siew Hoon
Zig Globulin
Diego Rondini
Madhavan Krishnan
Andrey Konovalov