From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [CONSOLIDATED PULL 01/20] bitbake.conf: Create staticlibs pacakge for static libraries
Date: Mon, 06 Jun 2011 09:50:34 -0700 [thread overview]
Message-ID: <4DED055A.8010200@linux.intel.com> (raw)
In-Reply-To: <1307357430.7672.7.camel@rex>
On 06/06/2011 03:50 AM, Richard Purdie wrote:
> On Mon, 2011-06-06 at 07:55 +0100, Phil Blundell wrote:
>> On Sun, 2011-06-05 at 23:44 -0700, Saul Wold wrote:
>>> SECTION_${PN}-dev = "devel"
>>> ALLOW_EMPTY_${PN}-dev = "1"
>>> RDEPENDS_${PN}-dev = "${PN} (= ${EXTENDPKGV})"
>>>
>>> +FILES_${PN}-staticlibs = "${libdir}/*.a ${base_libdir}/*.a"
>>> +SECTION_${PN}-staticlibs = "devel"
>>> +RDEPENDS_${PN}-staticlibs = "${PN}-dev (= ${EXTENDPV})"
>>
>> This should be ${EXTENDPKGV}, right?
>
> It should.
>
> I'm also not 100% convinced I like "-staticlibs" vs "-staticdev" as it
> doesn't feel consistent.
>
> The user gets exposed to these at the package manager level and will
> "xxx install xxx-staticX". The end result they'll get will be the
> installation of everything they need for static development (i.e. the
> -dev packages will get pulled in for the headers). This means they don't
> just result in the static libs as there are dependencies there. From the
> user perspective they are therefore packages for static development, not
> just the static libraries...
>
Richard,
I agree that they are for development and that by their nature they have
a dependency on the Development packages, but they contain libs only,
not all the development headers or tools, I think its therefore
mis-leading to call the package staticdev since they do not contain all
the development bits (they might depend on all the bits). It's a subtle
but important distinction.
As was pointed out earlier Fedora packages static libraries in a
"-static" package, but this had other implications for OE due to -static
already being in use (for busybox and mplayer), I am not sure that this
is not a problem for OE-Core, I would need to investigate. Meego also
seems to use the Fedora standard with "-static".
I still believe that -staticlibs is a better identifier for these packages.
Sau!
> Cheers,
>
> Richard
>
>
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2011-06-06 17:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 6:44 [CONSOLIDATED PULL 00/20] 05-June-2011 Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 01/20] bitbake.conf: Create staticlibs pacakge for static libraries Saul Wold
2011-06-06 6:55 ` Phil Blundell
2011-06-06 10:50 ` Richard Purdie
2011-06-06 16:50 ` Saul Wold [this message]
2011-06-06 17:31 ` Otavio Salvador
2011-06-06 19:00 ` Richard Purdie
2011-06-06 19:07 ` Otavio Salvador
2011-06-06 19:31 ` Richard Purdie
2011-06-07 10:08 ` Phil Blundell
2011-06-06 19:34 ` Koen Kooi
2011-06-06 14:59 ` Saul Wold
2011-06-06 17:03 ` Khem Raj
2011-06-06 19:01 ` Richard Purdie
2011-06-06 6:44 ` [CONSOLIDATED PULL 02/20] m4: upgrade from 1.4.15 to 1.4.16 Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 03/20] autoconf: upgrade from 2.65 to 2.68 Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 04/20] bison: upgrade from 2.4.3 to 2.5 Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 05/20] allarch.bbclass: Define BASE_PACKAGE_ARCH = "all" Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 06/20] util-linux_2.19.1.bb: Fix compliation on uclibc Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 07/20] base.bbclass: add cleansstate task between clean and cleanall Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 08/20] gnutls: use INC_PR on 2.12.5 version recipe Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 09/20] gnutls: add p11tool into gnutls-bin Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 10/20] package.bbclass: add support to split Qt translation files Saul Wold
2011-06-06 17:14 ` Richard Purdie
2011-06-06 17:27 ` Otavio Salvador
2011-06-06 19:29 ` Richard Purdie
2011-06-06 6:44 ` [CONSOLIDATED PULL 11/20] xf86-driver-common.inc: remove .la files to avoid unpackaged warning Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 12/20] gcc-package-cross: also install the symlinks in libexec with target prefix Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 13/20] shadow: recipe and patch cleanup Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 14/20] shadow: add a -native recipe with customized utilities Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 15/20] base-passwd: populate the target sysroot with passwd/group/login.defs Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 16/20] useradd.bbclass: new class for managing user/group permissions Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 17/20] useradd-example: example recipe for using inherit useradd Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 18/20] bitbake.conf: set PSEUDO_PASSWD within FAKEROOTENV Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 19/20] package_rpm.bbclass: make RPM use on-disk permissions Saul Wold
2011-06-06 6:44 ` [CONSOLIDATED PULL 20/20] tzcode: Update to 2011g Saul Wold
2011-06-07 20:40 ` [CONSOLIDATED PULL 00/20] 05-June-2011 Richard Purdie
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=4DED055A.8010200@linux.intel.com \
--to=sgw@linux.intel.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