[Buildroot] python Gobject

[Buildroot] python Gobject

[Freedreamer]

Hi All,

In my br rootfs I 've been using a lot of scripts based on python and a lot
of them are based on Gobject. Unfourtanetely when I try to start one I
always got a problem 'cause python misses the support for the Gobject.
Anyone can tell me what's the package I have to include in buildroot or if
there is a patch to apply to fully have them working ?


thanks in advance ,

have a nice day


Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140117/fb58d0e1/attachment.html>

[Buildroot] python Gobject

[Eric Le Bihan]

Hi!

On Fri, Jan 17, 2014 at 11:39:10AM +0100, Freedreamer wrote:

>    In my br rootfs I 've been using a lot of scripts based on python and a
>    lot of them are based on Gobject. Unfourtanetely when I try to start one I
>    always got a problem 'cause python misses the support for the Gobject.

Which versions of Python and GObject bindings are you using? Two combos are
possible:

1) Python 2.7 + Python-GObject < 2.28 (classic Python C bindings).
2) Python 3.x + Python-GObject > 3.x (bindings based on GObject introspection).

It looks like there are no packages (yet) for either one.
Packaging python-gobject 2.28 (also known as PyGtk) should be doable, but the
other combo requires to package gobject-introspection.

Best regards,
ELB

[Buildroot] python Gobject

[Freedreamer]

2014/1/17 Eric Le Bihan <eric.le.bihan.dev@free.fr>

> Hi!
>
> On Fri, Jan 17, 2014 at 11:39:10AM +0100, Freedreamer wrote:
>
> >    In my br rootfs I 've been using a lot of scripts based on python and
> a
> >    lot of them are based on Gobject. Unfourtanetely when I try to start
> one I
> >    always got a problem 'cause python misses the support for the Gobject.
>
> Which versions of Python and GObject bindings are you using? Two combos are
> possible:
>
> 1) Python 2.7 + Python-GObject < 2.28 (classic Python C bindings).
> 2) Python 3.x + Python-GObject > 3.x (bindings based on GObject
> introspection).
>
> It looks like there are no packages (yet) for either one.
> Packaging python-gobject 2.28 (also known as PyGtk) should be doable, but
> the
> other combo requires to package gobject-introspection.
>
> Best regards,
> ELB
>

Hi,

now i've been using python 2.7. you confirm there is no package?

Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140117/8941cb2c/attachment.html>

[Buildroot] python Gobject

[Eric Le Bihan]

On Fri, Jan 17, 2014 at 01:39:19PM +0100, Freedreamer wrote:
>    now i've been using python 2.7. you confirm there is no package?

Adding a new package for python-gobject 2.28 is pretty straightforward. I
did it in my repo:
https://github.com/elebihan/buildroot/commit/4107b0e4549aa4a234496c840361528381f57edf.

I wrote a test script where I subclassed gobject.GObject and tested it on an
emulated ARM platform: the code works without problems, though GLib emits a
warning about the props being initialized after class init.

Best regards,
ELB

[Buildroot] python Gobject

[sambuff]

Hi Eric,

> Adding a new package for python-gobject 2.28 is pretty straightforward. I
>did it in my repo:
https://github.com/elebihan/buildroot/commit/4107b0e4549aa4a234496c840361528381f57edf.

Thanks for the link but I've failed to build it though.

I've tried your new package with br-2013.11but the build fails because of
"missing python headers"

see the last lines :
"checking for python version... 2.7
checking for python platform... linux2
checking for python script directory...
${prefix}/lib/python2.7/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.7/site-packages
checking for python version... (cached) 2.7
checking for python platform... (cached) linux2
checking for python script directory... (cached)
${prefix}/lib/python2.7/site-packages
checking for python extension module directory... (cached)
${exec_prefix}/lib/python2.7/site-packages
checking for headers required to compile python extensions... not found
configure: error: could not find Python headers
make: ***
[/home/xxxxx/buildroot-2013.11/output/build/python-gobject-2.28.6/.stamp_configured]
Error 1"

I consider myself as "learning" how to use buildroot at the moment so I'm
may doing a mistake (but don't know where). If you had any advise that would
make my day.

Thanks for the good job.
Sam 



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/python-Gobject-tp60199p60414.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

[Buildroot] python Gobject

[Eric Le Bihan]

Hi!
On Mon, Jan 20, 2014 at 11:41:17PM -0800, sambuff wrote:
> > Adding a new package for python-gobject 2.28 is pretty straightforward. I
> >did it in my repo:
> https://github.com/elebihan/buildroot/commit/4107b0e4549aa4a234496c840361528381f57edf.
>
> Thanks for the link but I've failed to build it though.
>
> I've tried your new package with br-2013.11but the build fails because of
> "missing python headers"

D'Oh! I forgot to add 'python' after 'host-python' in
package/python-gobject/python-gobject.mk.

I reworked the package and added proper support for PyGtk. Development now
takes place in https://github.com/elebihan/buildroot/tree/pygtk-support/.
The complete stack has been added:

- python-pygobject (formerly python-gobject).
- python-xpyb.
- python-pycairo.
- python-pygtk.

Two demo boards (elebihan_demo_pygtk*) are available.
This is still WIP.

Thanks for your feedback.

Best regards,
ELB.

[Buildroot] python Gobject

[sambuff]

Eric Hi,

>D'Oh! I forgot to add 'python' after 'host-python' in
>package/python-gobject/python-gobject.mk.
>
>I reworked the package and added proper support for PyGtk. Development now
>takes place in https://github.com/elebihan/buildroot/tree/pygtk-support/.
>The complete stack has been added: 

Cool !  I'll take a look to pygtk also later on.

Regarding the 'python-gopbject' package I've tried to add 'python' after
'host-python' as you said. And I've also tried your new package in
https://github.com/elebihan/buildroot/tree/pygtk-support/. but I still have
the "missing headers" error. Haven't you got yourself this error with your
last branch ?

Thanks again :)
Sam



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/python-Gobject-tp60199p60535.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

[Buildroot] python Gobject

[Eric Le Bihan]

On Thu, Jan 23, 2014 at 03:27:32PM +0100, Samuel Buffet wrote:

I poked my nose in your build/python-pygobject-2.28.6/config.log. The
configure script of pygobject complains about not having found Python headers
because it fails to compile a test program:

> configure:14934: checking for headers required to compile python extensions
> configure:14954: /home/toto/Documents/homeproject/buildroot/output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-cpp -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I/home/toto/Documents/homeproject/buildroot/output/host/usr/include/python2.7 -I/home/toto/Documents/homeproject/buildroot/output/host/usr/include/python2.7 conftest.c
> In file included from /home/toto/Documents/homeproject/buildroot/output/host/usr/include/python2.7/Python.h:58:0,
>                  from conftest.c:26:
> /home/toto/Documents/homeproject/buildroot/output/host/usr/include/python2.7/pyport.h:849:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
> [...]
> configure:14959: result: not found
> configure:14961: error: could not find Python headers

Are you building a 32-bit ARM guest on a 64-bit host machine?
I dug into the mailing list and found this discussion, which seems to be
related to this problem:
http://lists.busybox.net/pipermail/buildroot/2011-August/045038.html.

Best regards,
ELB

[Buildroot] python Gobject

[Eric Le Bihan]

On Thu, Jan 23, 2014 at 06:02:56PM +0100, Eric Le Bihan wrote:
> I dug into the mailing list and found this discussion, which seems to be
> related to this problem:
> http://lists.busybox.net/pipermail/buildroot/2011-August/045038.html.
I've also found this interesting presentation about Python and
cross-compilation: http://whatschrisdoing.com/blog/talks/PyConTalk2012.pdf.

The author points out that cross-compiling Python extensions like
python-gobject, that do not rely on distutils, is likely to fail, because they
rely on the _host_ python-config to get the path to Python headers. In our
case, we end up with headers for a 64-bit machine
(host/usr/bin/include/python2.7) instead of the ones for the 32-bit target
(target/usr/include/python2.7).

I'll patch the autotools files in the modules of the PyGtk stack to handle
this properly.

Best regards,
ELB

[Buildroot] python Gobject

[sambuff]

Hello Eric,

Just FYI I've build your gobject package successfully on a 32-bit host so
you're last point was totally right.

Thanks
Sam-



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/python-Gobject-tp60199p60687.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

[Buildroot] python Gobject

[Eric Le Bihan]

> Just FYI I've build your gobject package successfully on a 32-bit host so
> you're last point was totally right.
I've found a x86_64 machine to perform tests. I've patched the configure.ac
files of the packages so that the path to the Python headers can be overriden
from Buildroot Makefiles. The fix is available in my branch.

Best regards,
ELB