Re: [PATCHv2 6/6] gdb/build: apply silent-rules.mk to the data-directory Makefile.in

[Andrew Burgess <aburgess@redhat.com>]

Simon Marchi <simark@simark.ca> writes:

> On 2024-04-06 13:03, Andrew Burgess wrote:
>
>> I've not managed to completely silence all of the recipe output, the
>> mkinstalldirs command outputs some diagnostic text which looks like
>> this:
>> 
>>     GEN    stamp-python
>>   mkdir -p -- ./python/gdb
>>   mkdir -p -- ./python/gdb/command
>>   mkdir -p -- ./python/gdb/dap
>>   mkdir -p -- ./python/gdb/function
>>   mkdir -p -- ./python/gdb/printer
>
> The output of these targets is a bit funny, "stamp-something".  It's as
> if the stamp file was the final artefact we're interested in, when in
> fact it's a build system detail.  Not a problem for me though.

Indeed.  We already have ECHO_GEN_XML_BUILTIN,
ECHO_GEN_XML_BUILTIN_GENERATED, and ECHO_INIT_C which are used as
alternatives to mentioning various 'stamp-*' targets.

I didn't do this because adding more and more new ECHO_GEN_* defines
just seemed unnecessary; seeing the stamp-* doesn't bother me, and this
is just something developers see, it's not for end users, so my
expectation is that folk will be able to ask, or dig into it if they
really care.

Plus, for some of the rules, like 'stamp-python' and 'stamp-guile',
where many things are done, it's not obvious what you'd replace the
'stamp-*' with.

That all said, if someone came along after and did add some custom
ECHO_GEN_* defines, I'm not going to stop them.

Thanks,
Andrew