Current location only maintains the latest archive and the releases are
often enough that we might not update that frequent
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Includes fix for CVE-2019-7733. Also adjust SRC_URI and use different mirror.
Signed-off-by: Joe Slater <joe.slater@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This gives users a proper error message when trying to build
a known non-building package.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Upstream has completely dropped including libio.h which makes it
redundant [1] moreover glibc is no longer shipping this header either
[1] 8564df1c8d
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The gnome class pulls in usually unwanted dependencies like gconf.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* fix the override in packagegroup-meta-oe.bb
* alllow building ne10 for armv7ve (e.g. Cortex-A15)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Use tar.bz2 instead of tar.gz since tar.gz doesn't exist for 2.1.0.
Signed-off-by: Hains van den Bosch <hainsvdbosch@ziggo.nl>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* to match what ne10 recipe does now
* fixes:
ERROR: Nothing PROVIDES 'ne10' (but meta-oe/recipes-multimedia/libopus/libopus_1.1.3.bb DEPENDS on or otherwise requires it)
ne10 was skipped: incompatible with machine qemuarm (not in COMPATIBLE_MACHINE)
ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'libopus', 'ne10']
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Upgrade to the latest release, 2.8.8.
Stop splitting the package up excessively, and use lib_package to put the
binaries into PN-bin.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Fetch was switched from tarball to git fetcher with release tag because
libvpx-1.7.0.tar.bz2 was not available at the previous download URL.
The download instructions for the project point to autogenerated
tarballs now (instead of storage.googleapis.com) [1], but archive
tarballs generated by git can end up with checksums that change
over time... so using git directly is less likely to break.
Successfully compile tested against:
* ffmpeg-4.0.2
* gstreamer1.0-plugins-good-1.14.2
* vlc-2.2.2
with vpx enabled in each respective PACKAGECONFIG.
[1] https://www.webmproject.org/code/releases/
Signed-off-by: S. Lockwood-Childs <sjl@vctlabs.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
waf script here does not support -o switch so define own which can
be run in B
Secondly, ensure to use python2
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Also remove two patches that have been merged upstream into v4l-util
since 1.12.3 and update the diff for patch 0002-contrib-* to prevent a
build warning.
Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Multiple -dbg packages per recipe is not encouraged, and only one is
recommended and the code only works properly in some cases for one.
Add RPROVIDES_${PN}-dbg to be compatiable with previous dbg packages
requiring.
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Restore minidlna recipe and bump it to v1.2.1
Move it to meta-multimedia
Signed-off-by: Baptiste Durand <baptiste.durand@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Commercial usage requires a license according to the homepage, so set
LICENSE_FLAGS = "commercial" to indicate that.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
WARNING:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
checking file utils/cec-compliance/Makefile.am
checking file utils/cec-ctl/Makefile.am
Hunk #1 succeeded at 6 (offset -1 lines).
checking file utils/cec-follower/Makefile.am
Hunk #1 succeeded at 7 with fuzz 1.
checking file utils/qv4l2/Makefile.am
checking file utils/v4l2-compliance/Makefile.am
checking file utils/v4l2-ctl/Makefile.am
and more
Signed-off-by: Armin Kuster <akuster808@gmail.com>
WARNING:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
checking file Makefile.am
Hunk #1 succeeded at 1 with fuzz 2.
amoung others
Signed-off-by: Armin Kuster <akuster808@gmail.com>
WARNING:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
checking file build/make/configure.sh
Hunk #1 succeeded at 581 with fuzz 2 (offset 137 lines).
Hunk #2 succeeded at 616 (offset 27 lines).
Signed-off-by: Armin Kuster <akuster808@gmail.com>
waf bbclass now expects waf to be an executable script
in ${S} before do_configure, otherwise it ends up in ugly python stack traces
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
