From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] Add python3 support
Date: Wed, 7 Nov 2012 16:01:19 +0100 [thread overview]
Message-ID: <1352300481-825-1-git-send-email-maxime.ripard@free-electrons.com> (raw)
Hi everyone,
After some hard work during the Buildroot dev days, here is the first attempt
at adding the python3 package to buildroot.
The patchset is actually smaller than for python2.7, even though we still carry
most of the patches, for several reasons:
- you can now pass a path to an external python interpreter directly using
the PYTHON_FOR_BUILD variable
- The building of the modules will detect if the headers and libs for a given
library are present so that it will build even if the libraries are missing
Maxime
Maxime Ripard (2):
Give the path to the realdelf binary the the packages
Add python3 package
package/Config.in | 1 +
package/Makefile.in | 2 +
package/python3/Config.in | 81 ++++++++++
...n3-3.3-000-generate-sysconfigdata-buildir.patch | 158 ++++++++++++++++++++
.../python3-3.3-001-support-for-build.patch | 68 +++++++++
.../python3-3.3-002-no-host-headers-libs.patch | 72 +++++++++
.../python3-3.3-003-staging-header-libs.patch | 41 +++++
...n3-3.3-004-no-import-when-cross-compiling.patch | 27 ++++
...python3-3.3-005-do-not-generate-pyo-files.patch | 40 +++++
.../python3-3.3-006-reread-environment.patch | 63 ++++++++
...ython3-3.3-007-change-pyconfig-h-location.patch | 76 ++++++++++
package/python3/python3-3.3-008-no-rpath.patch | 51 +++++++
.../python3-3.3-009-verbose-module-build.patch | 26 ++++
...3-010-distutils-cross-compilation-support.patch | 71 +++++++++
...python3-3.3-011-cross-compile-getaddrinfo.patch | 21 +++
package/python3/python3.mk | 152 +++++++++++++++++++
16 files changed, 950 insertions(+)
create mode 100644 package/python3/Config.in
create mode 100644 package/python3/python3-3.3-000-generate-sysconfigdata-buildir.patch
create mode 100644 package/python3/python3-3.3-001-support-for-build.patch
create mode 100644 package/python3/python3-3.3-002-no-host-headers-libs.patch
create mode 100644 package/python3/python3-3.3-003-staging-header-libs.patch
create mode 100644 package/python3/python3-3.3-004-no-import-when-cross-compiling.patch
create mode 100644 package/python3/python3-3.3-005-do-not-generate-pyo-files.patch
create mode 100644 package/python3/python3-3.3-006-reread-environment.patch
create mode 100644 package/python3/python3-3.3-007-change-pyconfig-h-location.patch
create mode 100644 package/python3/python3-3.3-008-no-rpath.patch
create mode 100644 package/python3/python3-3.3-009-verbose-module-build.patch
create mode 100644 package/python3/python3-3.3-010-distutils-cross-compilation-support.patch
create mode 100644 package/python3/python3-3.3-011-cross-compile-getaddrinfo.patch
create mode 100644 package/python3/python3.mk
--
1.7.9.5
next reply other threads:[~2012-11-07 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 15:01 Maxime Ripard [this message]
2012-11-07 15:01 ` [Buildroot] [PATCH 1/2] Give the path to the realdelf binary the the packages Maxime Ripard
2012-11-07 23:01 ` Peter Korsgaard
2012-11-07 15:01 ` [Buildroot] [PATCH 2/2] Add python3 package Maxime Ripard
2012-11-07 23:09 ` Peter Korsgaard
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=1352300481-825-1-git-send-email-maxime.ripard@free-electrons.com \
--to=maxime.ripard@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