From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python-pybind: new package
Date: Wed, 10 Jun 2020 22:55:23 +0200 [thread overview]
Message-ID: <20200610225523.5bc2d13b@windsurf.home> (raw)
In-Reply-To: <20200608213043.3443-1-guillaume.bressaix@gmail.com>
Hello Guillaume,
I've applied your patch, but after a number of changes. See below.
On Mon, 8 Jun 2020 23:30:43 +0200
"Guillaume W. Bres" <guillaume.bressaix@gmail.com> wrote:
> PyBind is a light (headers only) package
> for C++/Python and Python/C++ bindings.
>
> host-python-pybind is a dependency
> of my future contribution, so I added this feature.
This sort of comment should not go in the commit log, but below the
"---" sign that follows the Signed-off-by line. And in fact, I have
dropped the host variant: it should be added in the patch series
together with your "future contribution" that will need the host
variant of python-pybind.
> diff --git a/package/python-pybind/Config.in b/package/python-pybind/Config.in
> new file mode 100644
> index 0000000000..832a9fb971
> --- /dev/null
> +++ b/package/python-pybind/Config.in
> @@ -0,0 +1,10 @@
> +config BR2_PACKAGE_PYTHON_PYBIND
> + bool "python-pybind"
> + depends on BR2_PACKAGE_PYTHON3
Its documentation says Python 2.x is supported, so I've dropped this
"depends on".
> new file mode 100644
> index 0000000000..03cea1c060
> --- /dev/null
> +++ b/package/python-pybind/python-pybind.mk
> @@ -0,0 +1,15 @@
> +################################################################################
> +#
> +# python-pybind
> +#
> +################################################################################
> +
> +PYTHON_PYBIND_VERSION = 2.5.0
> +PYTHON_PYBIND_SOURCE = v$(PYTHON_PYBIND_VERSION).tar.gz
> +PYTHON_PYBIND_SITE = https://github.com/pybind/pybind11/archive
Here you should have use the "github" macro, because they anyway don't
provide their own tarballs, only automatically generated ones. This
also allows to have a better tarball name than v2.5.0.tar.gz.
> +$(eval $(python-package))
> +$(eval $(host-python-package))
So I said above, I've dropped this last line.
Applied with those changes. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-06-10 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 21:30 [Buildroot] [PATCH 1/1] python-pybind: new package Guillaume W. Bres
2020-06-10 20:55 ` Thomas Petazzoni [this message]
2020-06-11 18:14 ` Asaf Kahlon
2020-06-12 7:42 ` Guillaume Bres
2020-06-12 7:54 ` Guillaume Bres
2020-06-12 14:55 ` Asaf Kahlon
2020-06-12 16:01 ` Guillaume Bres
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=20200610225523.5bc2d13b@windsurf.home \
--to=thomas.petazzoni@bootlin.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