qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brian Cain <brian.cain@oss.qualcomm.com>
To: ltaylorsimpson@gmail.com, 'Anton Johansson' <anjo@rev.ng>,
	qemu-devel@nongnu.org
Cc: ale@rev.ng, philmd@linaro.org
Subject: Re: [PATCH 2/2] target/hexagon: Drop `ident` postprocess step
Date: Mon, 24 Mar 2025 22:12:46 -0500	[thread overview]
Message-ID: <e02be58e-9459-4799-8725-c7831169c89a@oss.qualcomm.com> (raw)
In-Reply-To: <001501db9d28$affce200$0ff6a600$@gmail.com>


On 3/24/2025 8:53 PM, ltaylorsimpson@gmail.com wrote:
>
>> -----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.


Aside: could using "clang-format" be another approach?  I suppose it's 
just exchanging one dependency for another, but maybe xcode comes w/this 
tool?  Then again, maybe it would be an inconvenient dependency on linux 
systems?



> Thanks,
> Taylor
>
>


  reply	other threads:[~2025-03-25  3:13 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
2025-03-25  3:12     ` Brian Cain [this message]
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=e02be58e-9459-4799-8725-c7831169c89a@oss.qualcomm.com \
    --to=brian.cain@oss.qualcomm.com \
    --cc=ale@rev.ng \
    --cc=anjo@rev.ng \
    --cc=ltaylorsimpson@gmail.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 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).