From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/5] python-cffi: add host variant
Date: Fri, 25 Dec 2015 20:00:59 +0100 [thread overview]
Message-ID: <20151225200059.48ac8dd7@free-electrons.com> (raw)
In-Reply-To: <CAGm1_kvud8TAWddmadKqMi+=Mpcfzx=XJ3KMgt2yB-otDq-DpQ@mail.gmail.com>
Dear Yegor Yefremov,
On Thu, 24 Dec 2015 23:12:49 +0100, Yegor Yefremov wrote:
> Target variant doesn't need pycparser. cffi's setup.py seems to
> distinguish, if we install real package or cross-compiled one:
>
> install_requires=[
> 'pycparser',
> ] if cpython else [],
I don't understand how this "if cpython" is relevant to make the
different between the native (host) variant or the cross-compiled
(target) variant. cpython is defined as is:
cpython = ('_cffi_backend' not in sys.builtin_module_names)
Can you give some more details?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-25 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 21:30 [Buildroot] [PATCH 1/5] python-ipaddress: new package Yegor Yefremov
2015-12-24 21:30 ` [Buildroot] [PATCH 2/5] python-pycparser: " Yegor Yefremov
2015-12-24 21:30 ` [Buildroot] [PATCH 3/5] python-cffi: add host variant Yegor Yefremov
2015-12-24 21:46 ` Yann E. MORIN
2015-12-24 22:12 ` Yegor Yefremov
2015-12-25 19:00 ` Thomas Petazzoni [this message]
2015-12-25 19:12 ` Yann E. MORIN
2015-12-25 19:58 ` Yegor Yefremov
2015-12-25 21:44 ` Yann E. MORIN
2015-12-26 22:54 ` Yegor Yefremov
2015-12-31 7:20 ` Oli Vogt
2015-12-31 8:55 ` Yegor Yefremov
2015-12-24 21:30 ` [Buildroot] [PATCH 4/5] python-cryptography: new package Yegor Yefremov
2015-12-24 21:30 ` [Buildroot] [PATCH 5/5] python-pyopenssl: " Yegor Yefremov
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=20151225200059.48ac8dd7@free-electrons.com \
--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