From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-devel <openembedded-devel@lists.openembedded.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe] State of bitbake world, test-dependencies 2014-12-11
Date: Thu, 11 Dec 2014 13:44:59 +0100 [thread overview]
Message-ID: <20141211124459.GC2467@jama> (raw)
In-Reply-To: <CAJTo0LYEvdspWOu=_LQTtD6xZTFZvHTyZpwQOEXbtpbSnPE-5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
On Thu, Dec 11, 2014 at 12:31:45PM +0000, Burton, Ross wrote:
> On 11 December 2014 at 12:14, Martin Jansa <martin.jansa@gmail.com> wrote:
>
> > > > WARN: gst-plugins-bad: gst-plugins-bad-meta rdepends on
> > > > gst-plugins-bad-rtmp, but it isn't a build dependency?
> > > > ERROR: gst-plugins-bad: gst-plugins-bad-rtmp package isn't created when
> > > > building with minimal dependencies?
> > > > ERROR: gst-plugins-bad: gst-plugins-bad-rtmp-dev package isn't created
> > > > when building with minimal dependencies?
> > > >
> > >
> > > Coincidently last night my world run gave me warnings that
> > > gst-plugins-bad-rtmp was depending on rtmpdump without a build depends,
> > so
> > > I've copied the PACKAGECONFIG[rtmp] from gstreamer1.0-plugins-bad to
> > > gst-plugins-bad. Presumably this will fix these errors, although that
> > > warning seems odd.
> >
> > Why odd? It just means that gst-plugins-bad-rtmp* packages aren't
> > created at all when rtmp isn't autodetected.
>
>
> But gst-plugins-bad-meta won't depend on -rtmp when rtmp isn't detected as
> the splitting is dynamically done.
gst-plugins-bad-meta depends on gst-plugins-bad-rtmp when built after
world (rtmp is detected) and doesn't depend on gst-plugins-bad-rtmp when
built in minimal TMPDIR.
test-dependencies.sh is showing this warning when the dependencies
between "maximal" and "minimal" builds aren't equal.
I still don't get what's wrong with that warning.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-12-11 12:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 9:23 State of bitbake world, test-dependencies 2014-12-11 Martin Jansa
2014-12-11 11:13 ` [oe] " Burton, Ross
2014-12-11 12:14 ` Martin Jansa
2014-12-11 12:31 ` Burton, Ross
2014-12-11 12:44 ` Martin Jansa [this message]
2014-12-11 13:54 ` Burton, Ross
2015-03-05 21:22 ` State of bitbake world, test-dependencies 2015-03-05 Martin Jansa
2015-03-06 6:27 ` Martin Jansa
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=20141211124459.GC2467@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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