All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Simon Glass <sjg@chromium.org>
Cc: Devicetree Compiler <devicetree-compiler@vger.kernel.org>
Subject: Re: [PATCH 1/2] README: Explain how to build with meson
Date: Thu, 29 Oct 2026 12:17:08 +1100	[thread overview]
Message-ID: <auKeh8KVIeaxW9Pp@gractus.seuss> (raw)
In-Reply-To: <20261028112007.3980089-1-sjg@chromium.org>

[-- Attachment #1: Type: text/plain, Size: 2846 bytes --]

On Wed, Oct 28, 2026 at 05:20:01AM -0600, Simon Glass wrote:
> Building with make is deprecated in favour of meson, but README.md only
> gives instructions for make, in its Python section, and CONTRIBUTING.md
> says to use 'make check'. The meson commands only appear in the warning
> which the Makefile prints.
> 
> Add a short Building section to README.md with the meson commands for
> building, testing and installing, pointing to the Meson quick guide and
> to scripts/install-deps.sh. Use meson for running the tests in
> CONTRIBUTING.md too.
> 
> Closes: https://github.com/dgibson/dtc/issues/83
> Assisted-by: Claude:claude-opus-5-5
> Signed-off-by: Simon Glass <sjg@chromium.org>

Reviewed-by: David Gibson <david@gibson.dropbear.id.au>

> ---
> 
>  CONTRIBUTING.md |  4 ++--
>  README.md       | 19 +++++++++++++++++++
>  2 files changed, 21 insertions(+), 2 deletions(-)
> 
> diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
> index 9742dc3..caf0210 100644
> --- a/CONTRIBUTING.md
> +++ b/CONTRIBUTING.md
> @@ -17,8 +17,8 @@ works with pylibfdt. If it cannot be supported, put the declaration in
>  
>  ## Tests
>  
> -Test files are kept in the `tests/` directory. Use `make check` to build and run
> -all tests.
> +Test files are kept in the `tests/` directory. Use `meson test -C build` to
> +build and run all tests (see [README.md](README.md#building)).
>  
>  If you want to adjust a test file, be aware that `tree_tree1.dts` is compiled
>  and checked against a binary tree from assembler macros in `trees.S`. So
> diff --git a/README.md b/README.md
> index 8f1a5d2..ed9039d 100644
> --- a/README.md
> +++ b/README.md
> @@ -8,6 +8,25 @@ dtc and libfdt are maintained by:
>  
>  * [David Gibson `<david@gibson.dropbear.id.au>`](mailto:david@gibson.dropbear.id.au)
>  
> +## Building
> +
> +dtc and libfdt are built with [Meson](https://mesonbuild.com/):
> +
> +```
> +$ meson setup build
> +$ meson compile -C build
> +$ meson test -C build
> +$ meson install -C build
> +```
> +
> +`meson configure build` lists the build options, e.g. `-Dpython=disabled`
> +to skip the Python library. See the
> +[Meson quick guide](https://mesonbuild.com/Quick-guide.html) for more,
> +such as installing with `--destdir`. `scripts/install-deps.sh` installs
> +the packages needed on common systems.
> +
> +Building with `make` still works but is deprecated.
> +
>  ## Python library
>  
>  A Python library wrapping libfdt is also available. To build this you
> ---
> base-commit: 1d50f3f8fa8bf9429eebb0769dafa5df37381ae1
> branch: readme-meson
> 
> -- 
> 2.43.0
> 
> 

-- 
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 --]

      parent reply	other threads:[~2026-10-29  1:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 11:20 [PATCH 1/2] README: Explain how to build with meson Simon Glass
2026-10-28 11:20 ` [PATCH 2/2] README: Use meson in the Python section Simon Glass
2026-10-28 20:05   ` Herve Codina
2026-10-29  1:17   ` David Gibson
2026-10-28 19:52 ` [PATCH 1/2] README: Explain how to build with meson Herve Codina
2026-10-29  1:17 ` 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=auKeh8KVIeaxW9Pp@gractus.seuss \
    --to=david@gibson.dropbear.id.au \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=sjg@chromium.org \
    /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.