DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 23.07 0/2] Minor meson build improvements
Date: Fri, 10 Mar 2023 11:11:36 +0000	[thread overview]
Message-ID: <20230310111138.92282-1-bruce.richardson@intel.com> (raw)

While experimenting with "muon" [1] as a replacement for meson, the
muon tool flagged a few issues that could do with being cleaned up
in our meson.build files. While currently muon is not in a position
to configure a DPDK build, it's not that far away from being able to
do so, so may be worth keeping an eye on it future. (Most
interestingly, it does contain a "muon fmt" tool for automatically
formatting meson.build files).

Marking these as for next release as it's late in the 23.03 cycle
as there is no point in taking a risk on these patches for such
minor issues.

[1] https://github.com/annacrombie/muon

Bruce Richardson (2):
  build: fix case of project language name
  build: explicitly track fil paths in current directory

 app/test/meson.build              | 2 +-
 buildtools/pkg-config/meson.build | 2 +-
 meson.build                       | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

--
2.37.2


             reply	other threads:[~2023-03-10 11:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 11:11 Bruce Richardson [this message]
2023-03-10 11:11 ` [PATCH 23.07 1/2] build: fix case of project language name Bruce Richardson
2023-03-13 23:50   ` Tyler Retzlaff
2023-03-10 11:11 ` [PATCH 23.07 2/2] build: explicitly track file paths in current directory Bruce Richardson
2023-03-13 23:50   ` Tyler Retzlaff
2023-05-24 20:24 ` [PATCH 23.07 0/2] Minor meson build improvements Thomas Monjalon

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=20230310111138.92282-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.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 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).