From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Python 3 external packages support
Date: Mon, 11 Feb 2013 16:54:09 +0100 [thread overview]
Message-ID: <20130211165409.2160e0cf@skate> (raw)
In-Reply-To: <CAHXCMMJnMGN5+2HbWkLoDwE37C=u5bHsZQm=2XPpAmJhJ2qTsQ@mail.gmail.com>
Dear Samuel Martin,
On Mon, 11 Feb 2013 16:45:58 +0100, Samuel Martin wrote:
> > Then, Python external modules would have to depend on
> > BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3 is they support both,
> > BR2_PACKAGE_PYTHON if they support Python 2 only, and
> > BR2_PACKAGE_PYTHON3 is they support Python 3 only.
>
> Also, keep in mind, that having a symlink python pointing to python3
> may/will break some build system,
> like scons (which does not yet support python3) and some other
> per-package ones.
It will only break if you allow such packages to be enabled when
Python3 is enabled. But true, some non-python related packages only need
the host python package, and for the host python package, we may want
to be able to build version 2, even if the target python is python 3.
The problem seems complex...
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-02-11 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 14:54 [Buildroot] [RFC] Python 3 external packages support Patrick
2013-02-11 15:09 ` Thomas Petazzoni
[not found] ` <1360595860.22602.YahooMailNeo@web171805.mail.ir2.yahoo.com>
[not found] ` <20130211162231.0ac06f9c@skate>
2013-02-11 15:40 ` Patrick
2013-02-11 15:42 ` Thomas Petazzoni
2013-02-11 15:45 ` Samuel Martin
2013-02-11 15:54 ` Thomas Petazzoni [this message]
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=20130211165409.2160e0cf@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