From: David Gibson <david@gibson.dropbear.id.au>
To: Eli Schwartz <eschwartz93@gmail.com>
Cc: devicetree-compiler@vger.kernel.org
Subject: Re: [PATCH v3 0/2] port python bindings to native Meson
Date: Thu, 1 May 2025 19:33:45 +0700 [thread overview]
Message-ID: <aBNqKYKOiT7WYYFp@zatzit> (raw)
In-Reply-To: <20250430152601.43554-1-eschwartz@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2908 bytes --]
On Wed, Apr 30, 2025 at 11:25:24AM -0400, Eli Schwartz wrote:
> Eli Schwartz (2):
> Makefile: deprecate in favor of Meson
> meson: port python bindings to build natively via meson and
> meson-python
Merged, thanks.
>
> MANIFEST.in | 12 -----
> Makefile | 53 ++-------------------
> libfdt/meson.build | 32 +++++++------
> meson.build | 3 +-
> meson_options.txt | 2 +
> pylibfdt/Makefile.pylibfdt | 30 ------------
> pylibfdt/meson.build | 28 +++++++----
> pyproject.toml | 33 +++++++++++++
> setup.py | 97 --------------------------------------
> 9 files changed, 77 insertions(+), 213 deletions(-)
> delete mode 100644 MANIFEST.in
> delete mode 100644 pylibfdt/Makefile.pylibfdt
> create mode 100644 pyproject.toml
> delete mode 100755 setup.py
>
> Range-diff against v2:
> 1: 142d7e4 ! 1: e5220b1 Makefile: deprecate in favor of Meson
> @@ Commit message
> true, we deprecate the latter and warn when you use it.
>
> GNU Make can emit a $(warning) on every Makefile run, which is a bit
> - noisly but means we don't need to have every target depend on a PHONY
> + noisy but means we don't need to have every target depend on a PHONY
> target (preventing built targets from being seen as up to date).
>
> ## Makefile ##
> @@ Makefile
> # Device Tree Compiler
> #
>
> -+$(warning WARNING: Building dtc using the Makefile is deprecated, in favor of using the Meson build system instead.)
> ++$(warning WARNING: Building dtc using make is deprecated, in favour of using Meson (https://mesonbuild.com))
> +$(warning )
> -+$(warning https://mesonbuild.com)
> -+$(warning )
> -+$(warning Use `meson setup builddir/ && ninja -C builddir/` to build, or `meson configure` to see build options.)
> ++$(warning Use `meson setup builddir/ && meson compile -C builddir/` to build, `meson test -C builddir/` to test, or `meson configure` to see build options.)
> +
> #
> # Version information will be constructed in this order:
> 2: 5d0590f ! 2: 3490690 meson: port python bindings to build natively via meson and meson-python
> @@ pyproject.toml (new)
> + 'License :: OSI Approved :: GNU General Public License v2 or later (GPLv2+)',
> + 'Operating System :: OS Independent',
> +]
> -+description = 'Pthon binding for libfdt'
> ++description = 'Python binding for libfdt'
> +readme = 'README.md'
> +requires-python = '>=3.8'
> +dynamic = ['version']
--
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 --]
next prev parent reply other threads:[~2025-05-01 12:33 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 ` David Gibson [this message]
2025-04-29 1:41 ` [PATCH v2 " Eli Schwartz
2025-04-30 14:59 ` David Gibson
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=aBNqKYKOiT7WYYFp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).