From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] ffmpeg: Add -dbg packages for all libraries
Date: Fri, 12 Feb 2016 08:32:08 +0000 [thread overview]
Message-ID: <1455265928.16142.269.camel@linuxfoundation.org> (raw)
In-Reply-To: <56BD97ED.1040802@mlbassoc.com>
On Fri, 2016-02-12 at 09:29 +0100, Gary Thomas wrote:
> On 2016-02-12 09:17, Richard Purdie wrote:
> > On Fri, 2016-02-12 at 04:58 +0100, Gary Thomas wrote:
> > > Improve the packaging of the libraries built by this recipe.
> > > These
> > > are created using special code in the recipe and the debug (-dbg)
> > > packages were not being created. Adding these packages allow the
> > > libraries in question to be debugged using GDB.
> >
> > This isn't really policy, the policy is one -dbg package per recipe
> > and
> > that is how the dependency chains and dbg-pkgs in IMAGE_FEATURES
> > work
> > and so on.
> >
> > I'm not arguing this is perfect, its not and I would like to see it
> > change. It is how it all works today though. Is there a pressing
> > reason
> > we need to do something different here?
>
> Without this change, none of the [renamed] libraries generated by
> the ffmpeg recipe have debug symbols available. As is, the recipe
> is generating separate -dev packages for each library - how is that
> different [policy-wise]?
>
> Should the -dev and -dbg info for the libraries be bundled into
> ffmpeg-dbg and ffmpeg-dev? Or perhaps the machinations generating
> the -dev packages in that recipe are just wrong?
There should only be one -dev package too.
As you saying the debug symbols are getting placed into the -dev
packages? They must be getting placed and hence packaged somewhere?
Cheers,
Richard
next prev parent reply other threads:[~2016-02-12 8:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 3:58 [PATCH] ffmpeg: Add -dbg packages for all libraries Gary Thomas
2016-02-12 8:17 ` Richard Purdie
2016-02-12 8:29 ` Gary Thomas
2016-02-12 8:32 ` Richard Purdie [this message]
2016-02-12 8:37 ` Gary Thomas
2016-02-12 10:40 ` Gary Thomas
2016-02-12 10:55 ` Burton, Ross
2016-02-12 10:49 ` Burton, Ross
2016-02-12 11:03 ` Gary Thomas
2016-02-12 11:11 ` Gary Thomas
2016-02-12 11:15 ` Burton, Ross
2016-02-12 15:36 ` 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=1455265928.16142.269.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox