Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] pkg-python infrastructure
Date: Sat, 26 Oct 2013 08:51:07 +0200	[thread overview]
Message-ID: <20131026085107.40230e6b@skate> (raw)
In-Reply-To: <OFCFB88498.0047424B-ON86257C0F.0057371F-86257C0F.0057386F@rockwellcollins.com>

Dear Ryan Barnett,

On Fri, 25 Oct 2013 10:52:54 -0500, Ryan Barnett wrote:

> A while back (about a week ago) - Gustavoz Zacarias, Thomas Petazzoni, and 
> myself - were having a conversation on the IRC about creating a new 
> package type for handling the builds of python packages. If I recall 
> correctly, this is what we discussed. I would like to just have some 
> record on how we want to handle building python packages.
> 
> Thomas P and Gustavoz - please correct/expand on any points that I may be 
> missing.
> 
> pkg-python infrastructure
> -------------------------
> 
>  * Would add a new makefile defining generic build steps for python 
> packages under package/pkg-python.mk.
> 
>  * Would support building for Python 2.7 and Python 3+.
> 
>  * Would ensure that cross-compiling of python packages is handled 
> correctly.
> 
>  * Would support setup.py and setuptools packages.
> 
> I don't know when I will be able to get around to doing this but I would 
> like to at least capture the points that were made. Also anyone else is 
> welcome to pick up this work too :)

I definitely confirm that the number of Python modules packages has
grown quite significantly, and that it is certainly time to look at
creating a common infrastructure for those that are based on
setup.py/setuptools. If anyone is interested in working on this, it'd
be great. I just want to warn that it doesn't look like an easy task,
as cross-compilation with Python can be a bit tricky.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2013-10-26  6:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 15:52 [Buildroot] [RFC] pkg-python infrastructure Ryan Barnett
2013-10-25 16:46 ` Thomas De Schampheleire
2013-10-26  6:51 ` Thomas Petazzoni [this message]
2013-10-26 10:01 ` Gustavo Zacarias
2013-12-04 23:05 ` Thomas Petazzoni
2013-12-05 10:47   ` Samuel Martin
2013-12-05 10:53     ` Thomas Petazzoni

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=20131026085107.40230e6b@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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