From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] python Gobject
Date: Tue, 21 Jan 2014 18:36:58 +0100 [thread overview]
Message-ID: <20140121173657.GA11605@pc-eric> (raw)
In-Reply-To: <1390290077263-60414.post@n4.nabble.com>
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.
next prev parent reply other threads:[~2014-01-21 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 10:39 [Buildroot] python Gobject Freedreamer
2014-01-17 11:31 ` Eric Le Bihan
2014-01-17 12:39 ` Freedreamer
2014-01-17 15:44 ` Eric Le Bihan
2014-01-21 7:41 ` sambuff
2014-01-21 17:36 ` Eric Le Bihan [this message]
2014-01-22 19:57 ` sambuff
[not found] ` <20140123134942.GA10856@pc-eric>
[not found] ` <CAGzWX_Jgdzctc_=-9XBg4Bw__KtdNwF3MChWvG4mi6XVNFUEhQ@mail.gmail.com>
2014-01-23 17:02 ` Eric Le Bihan
2014-01-24 18:27 ` Eric Le Bihan
2014-01-26 14:19 ` sambuff
2014-01-28 8:42 ` Eric Le Bihan
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=20140121173657.GA11605@pc-eric \
--to=eric.le.bihan.dev@free.fr \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox