Patchwork Added recipe for libconfig

libconfig can be used to parse a configuration file
in a structured language, but still compact and more
suitable for embedded devices compared to XML.

Signed-off-by: Stefano Babic <sbabic@denx.de>
---
 meta/recipes-support/libconfig/libconfig_1.4.8.bb |   15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 meta/recipes-support/libconfig/libconfig_1.4.8.bb

On Wed, Jun 13, 2012 at 10:19 AM, Stefano Babic <sbabic@denx.de> wrote:
> +PR = "r0"

Please drop the PR when using r0 as this is the default.

On 13 June 2012 14:19, Stefano Babic <sbabic@denx.de> wrote:
> libconfig can be used to parse a configuration file
> in a structured language, but still compact and more
> suitable for embedded devices compared to XML.

Is there a package that's actually going to use this in oe-core?

Ross

On 13/06/2012 16:02, Burton, Ross wrote:
> On 13 June 2012 14:19, Stefano Babic <sbabic@denx.de> wrote:
>> libconfig can be used to parse a configuration file
>> in a structured language, but still compact and more
>> suitable for embedded devices compared to XML.
> 
> Is there a package that's actually going to use this in oe-core?
> 

Hi Ross,

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 ?

Stefano

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?

Ross

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 ?

Stefano

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

On 14/06/2012 14:58, Philip Balister wrote:
>> 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 :)


Ok, thanks for clarification - I will send V2 for meta-oe.

Stefano