From: Philip Balister <philip@balister.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Added recipe for libconfig
Date: Thu, 14 Jun 2012 08:58:31 -0400 [thread overview]
Message-ID: <4FD9DFF7.70005@balister.org> (raw)
In-Reply-To: <4FD99A2B.2060006@denx.de>
On 06/14/2012 04:00 AM, Stefano Babic wrote:
> On 13/06/2012 16:24, Burton, Ross wrote:
>> On 13 June 2012 15:22, Stefano Babic <sbabic@denx.de> wrote:
>>> no, there is not yet. I add the libconfig to my image and my apllication
>>> make use of it. However, I see it as a general purpose library, that one
>>> can decide to add or not to the own rootfs.
>>>
>>> Is there some constraints in OE requiring that a lib can be merged only
>>> if a provided package make use of it ?
>>
>> Surely meta-oe would be a better place for this then?
>
> Understood. Or maybe under meta-yocto/recipes-core ? I will prefer this
> one because meta-oe is not part of the yocto distribution. Am I right to
> post patches here or am I completely off-topic ?
meta-oe is the place for this tyoe of recipe. The Yocto Project is not a
distribution, rather a project to make embedded systems easier :)
Philip
next prev parent reply other threads:[~2012-06-14 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 13:19 [PATCH] Added recipe for libconfig Stefano Babic
2012-06-13 13:34 ` Otavio Salvador
2012-06-13 14:02 ` Burton, Ross
2012-06-13 14:22 ` Stefano Babic
2012-06-13 14:24 ` Burton, Ross
2012-06-14 8:00 ` Stefano Babic
2012-06-14 12:58 ` Philip Balister [this message]
2012-06-14 14:27 ` Stefano Babic
-- strict thread matches above, loose matches on Subject: below --
2012-06-15 11:16 [meta-oe][PATCH V2] " Stefano Babic
2012-06-24 10:01 ` [PATCH V3] " Stefano Babic
2012-06-24 10:01 ` [PATCH] " Stefano Babic
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=4FD9DFF7.70005@balister.org \
--to=philip@balister.org \
--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 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.