Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] ffmpeg: Add -dbg packages for all libraries
Date: Fri, 12 Feb 2016 12:11:52 +0100	[thread overview]
Message-ID: <56BDBDF8.8020605@mlbassoc.com> (raw)
In-Reply-To: <56BDBC07.3060907@mlbassoc.com>

On 2016-02-12 12:03, Gary Thomas wrote:
> On 2016-02-12 11:49, Burton, Ross wrote:
>>
>> On 12 February 2016 at 03:58, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> 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.
>>
>>
>> oe-pkgdata-utils says:
>>
>> ffmpeg-dbg:
>>          /usr/bin/.debug/ffmpeg
>>          /usr/bin/.debug/ffprobe
>>          /usr/bin/.debug/ffserver
>>          /usr/lib/.debug/libavcodec.so.56.60.100
>>          /usr/lib/.debug/libavdevice.so.56.4.100
>>          /usr/lib/.debug/libavfilter.so.5.40.101
>>          /usr/lib/.debug/libavformat.so.56.40.101
>>          /usr/lib/.debug/libavutil.so.54.31.100
>>          /usr/lib/.debug/libpostproc.so.53.3.100
>>          /usr/lib/.debug/libswresample.so.1.2.101
>>          /usr/lib/.debug/libswscale.so.3.1.101
>>
>> So I'm not sure why this would be needed.
>>
>
> I'll check again, maybe it's as simple as ffmpeg-dbg wasn't
> brought in as an automatic dependency of mplayer2-dbg although
> a bunch of others were.
>

That's definitely it.  When I install mplayer2-dbg which was has
ffmpeg in DEPENDS, the library debug info was not found and ffmpeg-dbg
was not installed:

# opkg install mplayer2-dbg
Installing mplayer2-dbg (2.0+gitr0+2c378c71a4-r13.1) on root.
mplayer2-dbg: unsatisfied recommendation for libavformat-dbg
mplayer2-dbg: unsatisfied recommendation for libavutil-dbg
mplayer2-dbg: unsatisfied recommendation for libfaad-dbg
mplayer2-dbg: unsatisfied recommendation for libasound-dbg
mplayer2-dbg: unsatisfied recommendation for libavcodec-dbg
mplayer2-dbg: unsatisfied recommendation for libswresample-dbg
mplayer2-dbg: unsatisfied recommendation for libpostproc-dbg
mplayer2-dbg: unsatisfied recommendation for ncurses-libtinfo-dbg
mplayer2-dbg: unsatisfied recommendation for libswscale-dbg
...

So, how should this have worked, or is it a little broken?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2016-02-12 11:11 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
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 [this message]
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=56BDBDF8.8020605@mlbassoc.com \
    --to=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