From: Martin Jansa <martin.jansa@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: gstreamer without X11?
Date: Tue, 14 Jan 2014 14:47:54 +0100 [thread overview]
Message-ID: <20140114134754.GD3717@jama> (raw)
In-Reply-To: <52D53D02.1050207@mlbassoc.com>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
On Tue, Jan 14, 2014 at 06:34:58AM -0700, Gary Thomas wrote:
> On 2014-01-14 06:32, Burton, Ross wrote:
> > On 14 January 2014 13:18, Gary Thomas <gary@mlbassoc.com> wrote:
> >>> I don't understand why this happens though as the gst-plugins-base
> >>> recipe uses PKGCONFIG to control this:
> >>> PACKAGECONFIG ??= "${@base_contains('DISTRO___FEATURES', 'x11',
> >>> 'x11', '', d)}"
> >>> PACKAGECONFIG[x11] = "--enable-x --enable-xvideo,--disable-x
> >>> --disable-xvideo,virtual/__libx11 libxv libsm libice"
> >
> >
> > Check that gst-plugins-base resolved PACKAGECONFIG hasn't been
> > explicitly set somewhere (again, use bitbake -e gst-plugins-base).
>
> Not sure exactly what you mean, but this showed nothing as well:
> $ bitbake -e gst-plugins-base | grep PACKAGECONFIG
nothing? It should show at least assignment of empty value and a lot of
PACKAGECONFIG usages.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-01-14 13:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 13:07 gstreamer without X11? Gary Thomas
2014-01-14 13:12 ` Nicolas Dechesne
2014-01-14 13:18 ` Gary Thomas
2014-01-14 13:32 ` Burton, Ross
2014-01-14 13:34 ` Gary Thomas
2014-01-14 13:38 ` Nicolas Dechesne
2014-01-14 13:47 ` Martin Jansa [this message]
2014-01-14 13:55 ` Gary Thomas
2014-01-14 14:01 ` Nicolas Dechesne
2014-01-14 14:20 ` Burton, Ross
2014-01-14 14:20 ` Gary Thomas
2014-01-14 14:24 ` Burton, Ross
2014-01-14 14:30 ` Gary Thomas
2014-01-14 14:37 ` Burton, Ross
2014-01-14 14:49 ` Gary Thomas
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=20140114134754.GD3717@jama \
--to=martin.jansa@gmail.com \
--cc=gary@mlbassoc.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.