Patchwork Added recipe for libconfig

login
register
mail settings
Submitter Stefano Babic
Date June 13, 2012, 1:19 p.m.
Message ID <1339593545-14046-1-git-send-email-sbabic@denx.de>
Download mbox | patch
Permalink /patch/29789/
State New
Headers show

Comments

Stefano Babic - June 13, 2012, 1:19 p.m.
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
Otavio Salvador - June 13, 2012, 1:34 p.m.
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.
Ross Burton - June 13, 2012, 2:02 p.m.
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
Stefano Babic - June 13, 2012, 2:22 p.m.
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
Ross Burton - June 13, 2012, 2:24 p.m.
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
Stefano Babic - June 14, 2012, 8 a.m.
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
Philip Balister - June 14, 2012, 12:58 p.m.
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
Stefano Babic - June 14, 2012, 2:27 p.m.
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

Patch

diff --git a/meta/recipes-support/libconfig/libconfig_1.4.8.bb b/meta/recipes-support/libconfig/libconfig_1.4.8.bb
new file mode 100644
index 0000000..5b347b3
--- /dev/null
+++ b/meta/recipes-support/libconfig/libconfig_1.4.8.bb
@@ -0,0 +1,15 @@ 
+SUMMARY = "C/C++ Configuration File Library"
+DESCRIPTION = "processing of structured configuration files"
+SECTION = "libs"
+LICENSE = "LGPLv2.1"
+LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=fad9b3332be894bab9bc501572864b29"
+
+PR = "r0"
+
+SRC_URI = "http://www.hyperrealm.com/libconfig/libconfig-1.4.8.tar.gz \
+"
+
+SRC_URI[md5sum] = "36788da452e9fcfc8efb7661ef5d31ef"
+SRC_URI[sha256sum] = "18b1509fbf438a8c7f9b0af32284e458189b5f6dfd044f898926109f3c3c01ed"
+
+inherit autotools