All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Brabec <utx@penguin.cz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Revert "package bbclass: strip static libs as well"
Date: Sat, 24 Oct 2009 15:27:15 +0200	[thread overview]
Message-ID: <1256390835.4307.0@zaurus> (raw)
In-Reply-To: <hbuf0m$esa$1@ger.gmane.org> (from k.kooi@student.utwente.nl on Sat Oct 24 10:48:22 2009)

On Oct 24, 2009 at 10:48:22 Koen Kooi wrote:
> 
> I would be happy to take special care of the above recipe in my fixup 
> branch. Do we all agree that the above .a files need to go into -dev 
> packages? If so I'll add something like FILES_${PN}-static = "" to 
> the
> 
> affected recipes

All mentioned libraries above must go to -dev or -sdk, otherwise you
will not be able to build against them without -static installled.

FILES_${PN}-static = "" is not fully correct general solution. There
are projects, that have more static libraries. Only listed static
libraries must go to -dev, the rest may go to -static. A good
example is libsdl-x11. Only libSDLmain.a must go to -dev, the rest may
go to -static. I'll try to create smarter expression to find such
packages.

Note that this list covers only packages actually built for my image.

> And these wouldn't need special handling:

All of them probably would need. For example without libgcc.a you will
not be able to compile.

>  > gcc-4.3.3-r7.1: /usr/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/
> libgcc.a

-- 
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus




  reply	other threads:[~2009-10-24 13:28 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23  3:04 Revert "package bbclass: strip static libs as well" Holger Hans Peter Freyther
2009-10-23  7:23 ` Koen Kooi
2009-10-23  7:30   ` Holger Hans Peter Freyther
2009-10-23  7:58     ` Koen Kooi
2009-10-23  8:23       ` Holger Hans Peter Freyther
2009-10-23  8:36         ` Phil Blundell
2009-10-23  9:14           ` Koen Kooi
2009-10-23  9:33             ` Holger Hans Peter Freyther
2009-10-23  9:46               ` Koen Kooi
2009-10-23  9:54                 ` Holger Hans Peter Freyther
2009-10-23 10:03                   ` Koen Kooi
2009-10-23 10:24                   ` Phil Blundell
2009-10-23 11:07                 ` Stanislav Brabec
2009-10-23 11:34                   ` Holger Hans Peter Freyther
2009-10-23 22:31                     ` Stanislav Brabec
2009-10-24  0:29                       ` Khem Raj
2009-10-24  8:48                       ` Koen Kooi
2009-10-24 13:27                         ` Stanislav Brabec [this message]
2009-10-24 14:13                           ` Stanislav Brabec
2009-10-24 14:33                             ` Phil Blundell
2009-10-24 14:57                           ` Koen Kooi
2009-10-24 14:06                         ` Phil Blundell
2009-10-24 15:18                           ` Koen Kooi
2009-10-24 15:39                           ` Stanislav Brabec
2009-10-24 18:45                             ` Phil Blundell
2009-10-24 19:33                               ` Stanislav Brabec
2009-10-23 12:11                   ` Leon Woestenberg
2009-10-23 12:12                   ` Phil Blundell
2009-10-23 12:28               ` Koen Kooi
2009-10-23 12:37                 ` Phil Blundell
2009-10-23 12:42                 ` Phil Blundell
2009-10-23 12:56                   ` Koen Kooi
2009-10-24  2:32                     ` Holger Hans Peter Freyther
2009-10-24  3:42                       ` Denys Dmytriyenko
2009-10-24  8:40                       ` Koen Kooi
2009-10-23 18:21                   ` Denys Dmytriyenko
2009-10-23 18:36                     ` Phil Blundell
2009-10-23 19:53             ` Khem Raj
2009-10-23 18:26           ` Denys Dmytriyenko
2009-10-27  9:38 ` Koen Kooi
2009-10-27 10:21   ` Phil Blundell
2009-10-27 10:29     ` Koen Kooi
2009-10-27 10:50   ` Holger Hans Peter Freyther
2009-10-27 11:24     ` Koen Kooi

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=1256390835.4307.0@zaurus \
    --to=utx@penguin.cz \
    --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.