Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gst1-vaapi: new package
Date: Tue, 3 Jan 2017 13:37:31 +0100	[thread overview]
Message-ID: <20170103133731.7fa364e5@free-electrons.com> (raw)
In-Reply-To: <CALnvph0wzcSPGauyJ-SLfwTPf_sLLiwM=_Ac5=N2qysL7ZWS7Q@mail.gmail.com>

Hello,

On Tue, 3 Jan 2017 10:56:45 +0100, Jesper B?kdahl wrote:
> > OK. The configure.ac script indeed checks for plugins-base, but not for
> > plugins-bad.  
> 
> In configure.ac line 245 we have:
> AG_GST_CHECK_MODULES([GST_CODEC_PARSERS],
>   [gstreamer-codecparsers-$GST_API_VERSION], [$GST_PBADREQ], [yes])
> 
> which is checking for gstreamer-codecparsers that is part of plugins-bad?

Hum, ok. I haven't checked myself, but if you say so, fine :-)

> > Could you have a look at the configure.ac script? It seems like it
> > supports multiple renderers, not only DRM. If you don't want to support
> > all of them because you don't use them, that's fine. But you should
> > then use the appropriate --enable/--disable options to enable the right
> > renderer, and disable the other ones.  
> 
> I can add conditional CONF_OPTS that adds --enable/--disable based on
> which renderers can be built e.g.:
> ifeq ($(BR2_PACKAGE_LIBDRM),y)
> GST1_VAAPI_CONF_OPTS += --enable-drm
> else
> GST1_VAAPI_CONF_OPTS += --disable-drm
> endif

You can do that, *or* if you don't need those renderers, simply disable
them unconditionally for now. The next user interested in one renderer
or the other can tweak the .mk file and send a follow-up patch.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-01-03 12:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15 14:53 [Buildroot] [PATCH 1/1] gst1-vaapi: new package Jesper Bækdahl
2016-12-15 20:47 ` Thomas Petazzoni
2016-12-16 13:59   ` Jesper Bækdahl
2016-12-16 14:44     ` Thomas Petazzoni
2017-01-03  9:56       ` Jesper Bækdahl
2017-01-03 12:37         ` Thomas Petazzoni [this message]
2016-12-15 21:08 ` Peter Korsgaard
2016-12-16 14:03 ` Jesper Bækdahl
2016-12-16 14:03   ` [Buildroot] [PATCH v2 " Jesper Bækdahl
2017-03-12 20:53 ` [Buildroot] [PATCH " 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=20170103133731.7fa364e5@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