From: <ltaylorsimpson@gmail.com>
To: "'Anton Johansson'" <anjo@rev.ng>, <qemu-devel@nongnu.org>
Cc: <ale@rev.ng>, <brian.cain@oss.qualcomm.com>, <philmd@linaro.org>
Subject: RE: [PATCH 2/2] target/hexagon: Drop `ident` postprocess step
Date: Mon, 24 Mar 2025 20:53:20 -0500 [thread overview]
Message-ID: <001501db9d28$affce200$0ff6a600$@gmail.com> (raw)
In-Reply-To: <20250312194547.7364-3-anjo@rev.ng>
> -----Original Message-----
> From: Anton Johansson <anjo@rev.ng>
> Sent: Wednesday, March 12, 2025 2:46 PM
> To: qemu-devel@nongnu.org
> Cc: ale@rev.ng; ltaylorsimpson@gmail.com; brian.cain@oss.qualcomm.com;
> philmd@linaro.org
> Subject: [PATCH 2/2] target/hexagon: Drop `ident` postprocess step
>
> The indent command is not available on a default mac osx setup with xcode
> cli tools installed. While it does make idef-parser generated code nicer
to
> debug, it's not crucial and can be dropped.
>
> Signed-off-by: Anton Johansson <anjo@rev.ng>
> ---
> target/hexagon/meson.build | 21 ++-------------------
> 1 file changed, 2 insertions(+), 19 deletions(-)
>
> diff --git a/target/hexagon/meson.build b/target/hexagon/meson.build
> index abcf00ca1f..246dc7b241 100644
> --- a/target/hexagon/meson.build
> +++ b/target/hexagon/meson.build
> @@ -323,30 +323,13 @@ if idef_parser_enabled and 'hexagon-linux-user' in
> target_dirs
> command: [idef_parser, '@INPUT@', '@OUTPUT0@', '@OUTPUT1@',
> '@OUTPUT2@']
> )
>
> - indent = find_program('indent', required: false)
> - if indent.found()
> - idef_generated_tcg_c = custom_target(
> - 'indent',
> - input: idef_generated_tcg[0],
> - output: 'idef-generated-emitter.indented.c',
> - command: [indent, '-linux', '@INPUT@', '-o', '@OUTPUT@']
> - )
> - else
> - idef_generated_tcg_c = custom_target(
> - 'copy',
> - input: idef_generated_tcg[0],
> - output: 'idef-generated-emitter.indented.c',
> - command: ['cp', '@INPUT@', '@OUTPUT@']
> - )
> - endif
> -
I prefer to have the indented version present.
Is the above check/fallback not sufficient on MacOS? It works on a Linux
system where indent is not present.
Thanks,
Taylor
next prev parent reply other threads:[~2025-03-25 1:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 19:45 [PATCH 0/2] target/hexagon: Fix macOS build Anton Johansson via
2025-03-12 19:45 ` [PATCH 1/2] target/hexagon: Replace `prepare` script with meson target Anton Johansson via
2025-03-12 19:45 ` [PATCH 2/2] target/hexagon: Drop `ident` postprocess step Anton Johansson via
2025-03-25 1:53 ` ltaylorsimpson [this message]
2025-03-25 3:12 ` Brian Cain
2025-03-26 12:42 ` 'Anton Johansson' via
2025-04-02 3:25 ` Brian Cain
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='001501db9d28$affce200$0ff6a600$@gmail.com' \
--to=ltaylorsimpson@gmail.com \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=brian.cain@oss.qualcomm.com \
--cc=philmd@linaro.org \
--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 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.