From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/4] package/intel-mediadriver: new package
Date: Tue, 16 Apr 2019 22:26:51 +0200 [thread overview]
Message-ID: <20190416222651.0a74488d@windsurf> (raw)
In-Reply-To: <20190205181946.14496-2-lpdev@cordier.org>
Hello,
On Tue, 5 Feb 2019 19:19:43 +0100
Louis-Paul Cordier <lpdev@cordier.org> wrote:
> Signed-off-by: Louis-Paul Cordier <lpdev@cordier.org>
I have applied after doing a few changes, see below.
> diff --git a/package/intel-mediadriver/Config.in b/package/intel-mediadriver/Config.in
> new file mode 100644
> index 0000000000..7dd80fbfc7
> --- /dev/null
> +++ b/package/intel-mediadriver/Config.in
> @@ -0,0 +1,21 @@
> +config BR2_PACKAGE_INTEL_MEDIADRIVER
> + bool "intel-mediadriver"
> + depends on BR2_x86_64
> + depends on !BR2_STATIC_LIBS # mesa3D/libva
> + depends on BR2_INSTALL_LIBSTDCPP # mesa3D
> + depends on BR2_TOOLCHAIN_HAS_SYNC_1 # mesa3D
> + depends on BR2_TOOLCHAIN_HAS_THREADS # libva/libdrm/libpthread-stubs
> + depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL # mesa3D
mesa3D -> mesa3d
but more importantly, when you have dependencies, there should be
corresponding Config.in comments. So I've added:
+comment "intel-mediadriver needs X.org"
+ depends on BR2_x86_64 && BR2_TOOLCHAIN_HAS_SYNC_1
+ depends on !BR2_PACKAGE_XORG7
+
+comment "intel-mediadriver needs a toolchain w/ dynamic library, C++, NPTL"
+ depends on BR2_x86_64 && BR2_TOOLCHAIN_HAS_SYNC_1
+ depends on BR2_STATIC_LIBS || !BR2_INSTALL_LIBSTDCPP || \
+ !BR2_TOOLCHAIN_HAS_THREADS_NPTL
> +INTEL_MEDIADRIVER_VERSION = 18.4.0
> +INTEL_MEDIADRIVER_SITE = http://github.com/intel/media-driver/archive
> +INTEL_MEDIADRIVER_SOURCE= intel-media-$(INTEL_MEDIADRIVER_VERSION).tar.gz
> +INTEL_MEDIADRIVER_LICENSE = MIT,BSD-3-Clause
A space should have been used to separate the licenses.
Besides that, the build was failing with a non-SSP capable toolchain,
so I've added a quick patch
package/intel-mediadriver/0001-Drop-hardening-related-flags.patch to
drop -fstack-protector from the build flags.
Could you work on an improved solution that can be submitted upstream ?
The best solution is to provide an option to enable/disable usage of
hardening related options.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-16 20:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 18:19 [Buildroot] [PATCH v3 0/4] *** Add Intel QuickSync support to ffmpeg *** Louis-Paul Cordier
2019-02-05 18:19 ` [Buildroot] [PATCH v3 1/4] package/intel-mediadriver: new package Louis-Paul Cordier
2019-04-16 20:26 ` Thomas Petazzoni [this message]
2019-02-05 18:19 ` [Buildroot] [PATCH v3 2/4] package/intel-mediasdk: " Louis-Paul Cordier
2019-04-16 20:28 ` Thomas Petazzoni
2019-02-05 18:19 ` [Buildroot] [PATCH v3 3/4] package/ffmpeg: bump to version 4.1 Louis-Paul Cordier
2019-02-06 8:47 ` Thomas Petazzoni
2019-02-06 9:33 ` lpdev at cordier.org
2019-02-06 9:47 ` Thomas Petazzoni
2019-02-10 10:01 ` Bernd Kuhls
2019-02-10 10:27 ` Thomas Petazzoni
2019-02-10 18:53 ` Bernd Kuhls
2019-02-05 18:19 ` [Buildroot] [PATCH v3 4/4] package/ffmpeg: enable Intel QuickSync support Louis-Paul Cordier
2019-04-16 20:28 ` Thomas Petazzoni
2019-02-25 9:05 ` [Buildroot] [PATCH v3 0/4] *** Add Intel QuickSync support to ffmpeg *** lpdev at cordier.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190416222651.0a74488d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox