[Buildroot] msgpack-python (0.1.10) and libmsgpack (0.5.7) packaged for buildroot-2011.11

[Buildroot] msgpack-python (0.1.10) and libmsgpack (0.5.7) packaged for buildroot-2011.11

[Wojciech Zabolotny]

Hi,

I had to add two packages msgpack-python and libmsgpack to my embedded
system running Linux compiled with buildroot-2011.11
Unfortunately this version of buildroot does not support setuptools,
so I couldn't use the msgpack-python v. 0.2.0, and had to use older v.
0.1.10.
As my buildroot is compiled without C++ support, I had also to disable
the C++ API in libmsgpack.
Adding of those packages to buildroot required small modifications.
Attached is the patch, which adds definition for those packages in the
"package" directory.
Of course you'll need also to add lines:

source "package/libmsgpack/Config.in"
source "package/msgpack-python/Config.in"

in the appropriate section of the package/Config.in file
-- 
Regards,
Wojtek
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libmsgpack_and_msgpack-python.patch
Type: application/octet-stream
Size: 4171 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120707/a1803dc9/attachment.obj>

[Buildroot] msgpack-python (0.1.10) and libmsgpack (0.5.7) packaged for buildroot-2011.11

[Wojciech Zabolotny]

Ooops, I've generated the reversed patch.
Of course it should be applied with:
patch -p 0 -R < libmsgpack_and_msgpack-python.patch

Wojtek

[Buildroot] msgpack-python (0.1.10) and libmsgpack (0.5.7) packaged for buildroot-2011.11

[Thomas Petazzoni]

Hello Wojciech,

Le Sat, 7 Jul 2012 13:58:56 +0100,
Wojciech Zabolotny <wzab01@gmail.com> a ?crit :

> I had to add two packages msgpack-python and libmsgpack to my embedded
> system running Linux compiled with buildroot-2011.11
> Unfortunately this version of buildroot does not support setuptools,
> so I couldn't use the msgpack-python v. 0.2.0, and had to use older v.
> 0.1.10.
> As my buildroot is compiled without C++ support, I had also to disable
> the C++ API in libmsgpack.
> Adding of those packages to buildroot required small modifications.
> Attached is the patch, which adds definition for those packages in the
> "package" directory.

Thanks for this work!

Could you send a proper Git patch that contains all the needed
modification? We have a quick start guide on using Git to contribute to
Buildroot at http://elinux.org/Buildroot_how_to_contribute. If you have
questions about this, don't hesitate to ask.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] msgpack-python (0.1.10) and libmsgpack (0.5.7) packaged for buildroot-2011.11

[Wojciech Zabolotny]

On Fri Jul 13 21:13:31 UTC 2012
Thomas Petazzoni thomas.petazzoni at free-electrons.com  wrote:

| Could you send a proper Git patch that contains all the needed
| modification? We have a quick start guide on using Git to contribute to
| Buildroot at http://elinux.org/Buildroot_how_to_contribute. If you have
| questions about this, don't hesitate to ask.

I've tried to. However of course following the procedure described on
http://elinux.org/Buildroot_how_to_contribute
I've added my patch to the newest version of Buildroot.
In this case it could be possible to use newer version of msgpack-python
(and make the package dependent on python-setuptools).
Also someone better skilled in Buidlroot packaging could make the libmsgpack
C++ support configurable (I had to simply switch it off).

BTW. I can see the description message generated by the git in the
last buildroot Digest,
but not the patches themselves. Is it normal?

-- 
Regards,
Wojtek