From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/libva-utils: new package
Date: Sun, 2 Apr 2017 23:46:17 +0200 [thread overview]
Message-ID: <20170402234617.5ff597dd@free-electrons.com> (raw)
In-Reply-To: <20170402081327.2195-3-bernd.kuhls@t-online.de>
Hello,
On Sun, 2 Apr 2017 10:13:27 +0200, Bernd Kuhls wrote:
> The utils provided by this package were formerly packaged with libva.
> Libva contained a patch not to compile mpeg2vldemo to reduce
> dependencies by avoiding C++, this patch is not moved to this package.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/Config.in | 1 +
> package/libva-utils/Config.in | 15 +++++++++++++++
> package/libva-utils/libva-utils.hash | 4 ++++
> package/libva-utils/libva-utils.mk | 14 ++++++++++++++
Entry to DEVELOPERS file is missing.
> diff --git a/package/Config.in b/package/Config.in
> index d6d134d0c..364766e37 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -1049,6 +1049,7 @@ menu "Graphics"
> source "package/libsvgtiny/Config.in"
> source "package/libva/Config.in"
> source "package/libva-intel-driver/Config.in"
> + source "package/libva-utils/Config.in"
Does it really makes sense to have this package in Libraries->Graphics
when it is in fact not a library at all?
> diff --git a/package/libva-utils/Config.in b/package/libva-utils/Config.in
> new file mode 100644
> index 000000000..89615cad3
> --- /dev/null
> +++ b/package/libva-utils/Config.in
> @@ -0,0 +1,15 @@
> +config BR2_PACKAGE_LIBVA_UTILS
> + bool "libva-utils"
> + select BR2_PACKAGE_LIBVA
> + depends on BR2_INSTALL_LIBSTDCPP
> + depends on BR2_TOOLCHAIN_HAS_THREADS # libva
> + depends on !BR2_STATIC_LIBS # libva
Perhaps this can be summarized as:
depends on BR2_PACKAGE_LIBVA
indeed, someone wanting the libva tests will surely realize that he
needs to enable libva in the first place, no?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-02 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 8:13 [Buildroot] [PATCH 1/3] package/libva: bump version to 1.8.0 Bernd Kuhls
2017-04-02 8:13 ` [Buildroot] [PATCH 2/3] package/libva-intel-driver: " Bernd Kuhls
2017-04-02 21:45 ` Thomas Petazzoni
2017-04-02 8:13 ` [Buildroot] [PATCH 3/3] package/libva-utils: new package Bernd Kuhls
2017-04-02 21:46 ` Thomas Petazzoni [this message]
2017-04-03 13:33 ` Arnout Vandecappelle
2017-04-02 21:45 ` [Buildroot] [PATCH 1/3] package/libva: bump version to 1.8.0 Thomas Petazzoni
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=20170402234617.5ff597dd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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