From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL 5/5] hexagon: use env keyword argument to pass PYTHONPATH
Date: Sun, 14 Mar 2021 18:50:25 +0100 [thread overview]
Message-ID: <20210314175025.114723-6-pbonzini@redhat.com> (raw)
In-Reply-To: <20210314175025.114723-1-pbonzini@redhat.com>
This feature is new in meson 0.57 and allows getting rid of the "env" wrapper.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
target/hexagon/meson.build | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/target/hexagon/meson.build b/target/hexagon/meson.build
index bb0b4fb621..aaeee11ac1 100644
--- a/target/hexagon/meson.build
+++ b/target/hexagon/meson.build
@@ -156,7 +156,8 @@ dectree_generated = custom_target(
'dectree_generated.h.inc',
output: 'dectree_generated.h.inc',
depends: [iset_py],
- command: ['env', 'PYTHONPATH=' + meson.current_build_dir(), files('dectree.py'), '@OUTPUT@'],
+ env: {'PYTHONPATH': meson.current_build_dir()},
+ command: [python, files('dectree.py'), '@OUTPUT@'],
)
hexagon_ss.add(dectree_generated)
--
2.29.2
next prev parent reply other threads:[~2021-03-14 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 17:50 [PULL 0/5] Meson version update Paolo Bonzini
2021-03-14 17:50 ` [PULL 1/5] hexagon: do not specify executables as inputs Paolo Bonzini
2021-03-14 17:50 ` [PULL 2/5] hexagon: do not specify Python scripts " Paolo Bonzini
2021-03-14 17:50 ` [PULL 3/5] meson: bump submodule to 0.57.1 Paolo Bonzini
2021-03-14 17:50 ` [PULL 4/5] meson: switch minimum meson version to 0.57.0 Paolo Bonzini
2021-03-14 17:50 ` Paolo Bonzini [this message]
2021-03-15 16:59 ` [PULL 0/5] Meson version update Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2021-03-15 17:39 [PULL v2 " Paolo Bonzini
2021-03-15 17:39 ` [PULL 5/5] hexagon: use env keyword argument to pass PYTHONPATH Paolo Bonzini
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=20210314175025.114723-6-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).