emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Android port


From: Bruno Haible
Subject: Re: Android port
Date: Sun, 06 Aug 2023 13:02:45 +0200

Eli Zaretskii wrote:
> Isn't there some "summary" variable for printf, like
> gl_cv_func_printf_works or some such, which is set if all of the above
> variables are set?  I'd prefer to override summary if it exists

No, there is no such "summary" variable. And it would be overkill to
introduce one, because
  - Emacs is the only package that needs a certain Gnulib module on
    most platforms but wants to deactivate it on one particular platform.
    Other packages don't work this way.
  - The approach to set the variables individually in mingw-cfg.site
    is good enough. It occasionally needs updates, every N years or so,
    when some variable is added. But that's not a good enough justification
    for adding complexity to Gnulib.

Also, a "summary" variable would not fulfil the goal that you set out
yourself yesterday:
  "I prefer not to preset gl_cv_* variables in this case, since they are
   general enough tests of specific printf features, and if those
   features will ever be really needed in Emacs, we want to be alerted to
   that."

I perfectly understand this argument, that you want to be aware if the
mingw-cfg.site file for example pretends that Emacs does not need %b support,
in order to check the format strings to see whether that's indeed the case.
The individual gl_cv_* variables are the right instrument to achieve this
process.

Bruno






reply via email to

[Prev in Thread] Current Thread [Next in Thread]