From: David Gibson <david@gibson.dropbear.id.au>
To: Eli Schwartz <eschwartz93@gmail.com>
Cc: devicetree-compiler@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Makefile: deprecate in favor of Meson
Date: Wed, 30 Apr 2025 22:20:33 +0700 [thread overview]
Message-ID: <aBI_wad4TnNRCTWA@zatzit> (raw)
In-Reply-To: <4abaf886-440f-48ec-b133-899111f3aec2@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
On Wed, Apr 30, 2025 at 11:10:20AM -0400, Eli Schwartz wrote:
> On 4/30/25 10:56 AM, David Gibson wrote:
> >> +$(warning WARNING: Building dtc using the Makefile is deprecated, in favor of using the Meson build system instead.)
> >> +$(warning )
> >> +$(warning https://mesonbuild.com)
> >
> > For succinctness, I suggest:
> >
> > WARNING: Building dtc using make is deprecated in favour of using Meson (https://mesonbuild.com)
> >
> > Note that British/Australian spelling is preferred for this project, hence "favour".
>
>
> Yup, sounds reasonable. :)
>
>
> >> +$(warning )
> >> +$(warning Use `meson setup builddir/ && ninja -C builddir/` to build, or `meson configure` to see build options.)
> >
> > I'd prefer to suggest "meson compile -C builddir" here, rather than
> > directly invoking ninja, and I'd also like to list "meson test -C
> > builddir" as the replacement for "make check".
>
>
> As you wish, of course. But note that "meson compile" is a dispatching
> command that first checks whether the build has been setup using a
> non-default --backend option instead of the default ninja:
>
> - Microsoft msbuild
> - Apple xcode
>
> and then determines which of the three to run. So if you decide to run
> "meson compile -C builddir/" it will just in turn run, on your behalf,
> "ninja -C builddir/".
I'm aware.
> It also has the side effect of, if your compiler is MSVC cl.exe, loading
> vcvarsall.bat before dispatching to ninja, as a workaround for
>
> https://github.com/ninja-build/ninja/issues/1610
>
> None of that matters for dtc, I guess. :)
Well.. maybe. Since it's not tested, it probably doesn't work, but
AFAIK there's no inherent reason dtc couldn't be built on MSVC or
xcode. That's why I'd prefer to list the more broadly correct
command.
--
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-04-30 15:20 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 [this message]
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
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=aBI_wad4TnNRCTWA@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).