From: GNUtoo <GNUtoo@no-log.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] -dbg for static libraries?
Date: Sat, 19 Sep 2009 23:48:46 +0200 [thread overview]
Message-ID: <1253396926.1456.14.camel@localhost> (raw)
In-Reply-To: <1253188893.12689.556.camel@mill.internal.reciva.com>
On Thu, 2009-09-17 at 13:01 +0100, Phil Blundell wrote:
> On Thu, 2009-09-17 at 01:40 -0400, Denys Dmytriyenko wrote:
> > Would it make sense to package stripped version of a static lib into -dev and
> > the full version into corresponding -dbg?
>
> I'm not sure that you'd want the debugging .a file in -dbg itself, since
> the -dbg packages are for installation on the target device and the .a
> libraries would be useless there.
>
> Punting the debug versions of the .a libraries into a new package
> (-static-dbg or some such) wouldn't be a bad idea. Or, for SDK
> purposes, you could even consider ditching the .a libraries altogether
> for packages that have a .so since virtually nobody is going to be doing
> static linking in this day and age.
I often do static linking for different reasons:
*different libc on the target(like with android for instance)
*debugging(like in the case where all shared libs segfaulted on mips
+uclibc,I needed a static gdb,a static strace etc...)
Denis
next prev parent reply other threads:[~2009-09-19 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 5:40 [RFC] -dbg for static libraries? Denys Dmytriyenko
2009-09-17 9:46 ` Koen Kooi
2009-09-17 12:16 ` Stanislav Brabec
2009-09-17 12:01 ` Phil Blundell
2009-09-19 21:48 ` GNUtoo [this message]
2009-09-20 7:13 ` Phil Blundell
2009-09-20 11:45 ` GNUtoo
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=1253396926.1456.14.camel@localhost \
--to=gnutoo@no-log.org \
--cc=openembedded-devel@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 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.