From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: add "python-package CFFI backend" section
Date: Tue, 23 Feb 2016 21:07:40 +0100 [thread overview]
Message-ID: <56CCBC0C.1060709@mind.be> (raw)
In-Reply-To: <1456132859-8459-1-git-send-email-yegorslists@googlemail.com>
On 02/22/16 10:20, yegorslists at googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Hi Yegor,
A few forgotton words as indicated below.
Also, Peter, have you given some thought to my proposal of requiring the
http://dustycloud.org/blog/vcs-friendly-patchable-document-line-wrapping/
line wrapping style for new documentation patches?
> ---
> docs/manual/adding-packages-python.txt | 36 ++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
>
> diff --git a/docs/manual/adding-packages-python.txt b/docs/manual/adding-packages-python.txt
> index 588dbf8..3278998 100644
> --- a/docs/manual/adding-packages-python.txt
> +++ b/docs/manual/adding-packages-python.txt
> @@ -160,3 +160,39 @@ possible to customize what is done in any particular step:
> +PYTHON_FOO_BUILD_CMDS+ variable, it will be used instead of the
> default Python one. However, using this method should be restricted
> to very specific cases. Do not use it in the general case.
> +
> +[[python-package-cffi-backend]]
> +
> +==== +python-package+ CFFI backend
> +
> +C Foreign Function Interface for Python (CFFI) provides a convenient and
> +reliable way to call compiled C code from Python using interface declarations
> +written in C. Python packages relying on this backend can be identified by
> +appearance of +cffi+ dependency in an +install_requires+ field of their
appearance of the +cffi+ dependency
> ++setup.py+ file.
> +
> +Such a package needs +python-cffi+ as a runtime dependency in order to import
> +compiled C library wrapper on a target and +host-python-cffi+ as a build-time
the compiled C library wrapper on the target, and +host-python-cffi+ as a ...
> +dependency in order to cross-compile the C wrapper. You'll need to add following
You'll need to add the following code
> +code to you package's +Config.in+ and +*.mk+ files respectively:
to the package's +Config.in+ and +*.mk+ files, respectively.
Regards,
Arnout
> +
> +
> +------------------------
> +config BR2_PACKAGE_PYTHON_FOO
> + bool "python-foo"
> + select BR2_PACKAGE_PYTHON_CFFI # runtime
> +------------------------
> +
> +------------------------
> +################################################################################
> +#
> +# python-foo
> +#
> +################################################################################
> +
> +...
> +
> +PYTHON_FOO_DEPENDENCIES = host-python-cffi
> +
> +$(eval $(python-package))
> +------------------------
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-23 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 9:20 [Buildroot] [PATCH] docs/manual: add "python-package CFFI backend" section yegorslists at googlemail.com
2016-02-23 20:07 ` Arnout Vandecappelle [this message]
2016-02-24 14:37 ` 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=56CCBC0C.1060709@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.