Re: Merging feature/android

[Eli Zaretskii]

> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org,  eggert@cs.ucla.edu
> Date: Fri, 03 Mar 2023 08:51:11 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Po Lu <luangruo@yahoo.com>
> >> Cc: emacs-devel@gnu.org,  eggert@cs.ucla.edu
> >> Date: Thu, 02 Mar 2023 21:42:30 +0800
> >> 
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >> 
> >> > Rewriting the configury is OK, but that still doesn't need
> >> > ifavailable, AFAIU.  For example, we build with HarfBuzz if that is
> >> > available, but we don't use ifavailable for it.  How is this one
> >> > different?
> >> 
> >> Well, it would be a nasty shock for someone to configure --with-modules,
> >> and not get an error when dynamic modules cannot be used.
> >
> > I'm talking about the default case, where there's no --with-modules
> > option explicitly in the configure command line.  If the user does
> > explicitly asks for modules, then emitting an error message is
> > reasonable.  But if the user didn't ask for that explicitly, why not
> > silently disable the feature, like we do with HarfBuzz and others?
> 
> The HarfBuzz check doesn't behave that way, since it doesn't use
> ifavailable.  ``--with-modules'' does, however.

I don't understand your reasoning, and more importantly, I don't
understand the conclusion.  Do you agree that ifavailable shouldn't be
needed in this case?  If not, please explain more, because I don't
think I understand what you say above.