From: David Gibson <david@gibson.dropbear.id.au>
To: Eli Schwartz <eschwartz93@gmail.com>
Cc: devicetree-compiler@vger.kernel.org
Subject: Re: [PATCH v2 2/2] meson: port python bindings to build natively via meson and meson-python
Date: Wed, 30 Apr 2025 21:59:58 +0700 [thread overview]
Message-ID: <aBI67qC9Z6z3T-pu@zatzit> (raw)
In-Reply-To: <20250429014241.90681-3-eschwartz@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
On Mon, Apr 28, 2025 at 09:41:43PM -0400, Eli Schwartz wrote:
> We get full build parallelism and fewer confusing ancient distutils
> paths. The python wheels build fully standalone, including linking
> libfdt as a static library.
>
> For convenience, when running pip install a meson option is passed that
> prevents building tools or installing headers/pkgconfig files.
> meson-python would otherwise include them in the wheel itself, in case
> they are needed, but this is essentially a bit useless so don't bother.
>
> The old setuptools-based build is now redundant and goes away.
>
> Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
LGTM, excepting one tiny typo
[snip]
> diff --git a/pyproject.toml b/pyproject.toml
> new file mode 100644
> index 0000000..8682026
> --- /dev/null
> +++ b/pyproject.toml
> @@ -0,0 +1,33 @@
> +[build-system]
> +build-backend = 'mesonpy'
> +requires = ['meson-python']
> +
> +[project]
> +name = 'libfdt'
> +authors = [
> + {name = 'Simon Glass', email = 'sjg@chromium.org'},
> +]
> +classifiers = [
> + 'Programming Language :: Python :: 3',
> + 'License :: OSI Approved :: BSD License',
> + 'License :: OSI Approved :: GNU General Public License v2 or later (GPLv2+)',
> + 'Operating System :: OS Independent',
> +]
> +description = 'Pthon binding for libfdt'
"Pthon"
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-04-30 15:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 0:40 [PATCH] meson: port python bindings to build natively via meson and meson-python Eli Schwartz
2025-03-18 14:15 ` Rob Herring
2025-03-18 14:36 ` Eli Schwartz
2025-03-18 17:02 ` Rob Herring
2025-03-19 6:51 ` Eli Schwartz
2025-03-19 5:55 ` David Gibson
2025-03-19 6:30 ` Eli Schwartz
2025-04-25 7:56 ` David Gibson
2025-04-29 1:34 ` Eli Schwartz
2025-04-29 1:41 ` [PATCH v2 0/2] port python bindings to native Meson Eli Schwartz
2025-04-29 1:41 ` [PATCH v2 1/2] Makefile: deprecate in favor of Meson Eli Schwartz
2025-04-30 14:56 ` David Gibson
2025-04-30 15:10 ` Eli Schwartz
2025-04-30 15:20 ` David Gibson
2025-04-30 15:25 ` [PATCH v3 0/2] port python bindings to native Meson Eli Schwartz
2025-04-30 15:25 ` [PATCH v3 1/2] Makefile: deprecate in favor of Meson Eli Schwartz
2025-04-30 15:25 ` [PATCH v3 2/2] meson: port python bindings to build natively via meson and meson-python Eli Schwartz
2025-05-01 12:33 ` [PATCH v3 0/2] port python bindings to native Meson David Gibson
2025-04-29 1:41 ` [PATCH v2 2/2] meson: port python bindings to build natively via meson and meson-python Eli Schwartz
2025-04-30 14:59 ` David Gibson [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=aBI67qC9Z6z3T-pu@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=eschwartz93@gmail.com \
/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.