From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [RFC - Staticdev 1/2] multiple recipes converted to -staticdev packages
Date: Tue, 28 Jun 2011 16:51:44 -0700 [thread overview]
Message-ID: <4E0A6910.4040107@linux.intel.com> (raw)
In-Reply-To: <B39BDB9E-CF2E-47CD-A195-BCEFD4B8B8C4@dominion.thruhere.net>
On 06/26/2011 12:34 AM, Koen Kooi wrote:
>
> Op 26 jun 2011, om 06:36 heeft Saul Wold het volgende geschreven:
>
>> This commit adds a new base package ${PN}-staticdev to
>> bitbake.conf which pulls in the static *.a libraries as
>> a seperate package, it filters out the nonshared.a
>> libraries where appropriate.
>>
>> Additional this commit adds a new libdev.bbclass which provides
>> a set of macros and variables to convert ${PN} to lib${PN},
>> which a number of recipes where then converted to use.
>
> Can't that be merged into lib_package.bbclass?
>
I looked into this further, and I think that lib_package serves a
different purpose than libdev and it would be wrong to inherit from
lib_package.
lib_package seems to split out binaries from the core ${PN} package and
places them in ${PN}-bin. I did update it to move static libraries to
the -staticdev package.
Sau!
> _______________________________________________
> 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-28 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 4:36 [RFC - Staticdev 0/2] Move static libraries to -staticdev packages Saul Wold
2011-06-26 4:36 ` [RFC - Staticdev 1/2] multiple recipes converted " Saul Wold
2011-06-26 7:34 ` Koen Kooi
2011-06-27 6:16 ` Saul Wold
2011-06-28 23:51 ` Saul Wold [this message]
2011-06-26 4:36 ` [RFC - Staticdev 2/2] systemtap: add sqlite3 to DEPENDS Saul Wold
2011-06-27 9:57 ` Phil Blundell
2011-06-28 5:59 ` Saul Wold
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=4E0A6910.4040107@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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