Re: Merging feature/android

[Po Lu]

XPM is actually a good example of what I'm talking about: it is used by default 
only if the system in question typically has libXpm preinstalled.  Otherwise, 
the built-in XPM code in image.c is used instead.  This happens on PGTK, 
Android and Mac OS.

On March 7, 2023 9:36:14 PM GMT+08:00, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Po Lu <luangruo@yahoo.com>
>> Cc: arsen@aarsen.me,  eggert@cs.ucla.edu,  emacs-devel@gnu.org
>> Date: Tue, 07 Mar 2023 21:03:06 +0800
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> >> From: Po Lu <luangruo@yahoo.com>
>> >> Cc: arsen@aarsen.me,  eggert@cs.ucla.edu,  emacs-devel@gnu.org
>> >> Date: Tue, 07 Mar 2023 08:36:16 +0800
>> >> 
>> >> Eli Zaretskii <eliz@gnu.org> writes:
>> >> 
>> >> >> > Once again, let's please make this work like configure does with 
>> >> >> > image
>> >> >> > libraries, i.e. error out by default if modules aren't supported, and
>> >> >> > suggest using ifavailable.  This will solve the problem cleanly and 
>> >> >> > in
>> >> >> > a way that cannot be missed by chance.
>> >> >> 
>> >> >> How about only on GNU/Linux systems, and maybe Mac OS and Windows?
>> >> >
>> >> > I don't understand what you propose, in practical terms.
>> >> 
>> >> Basically, to only default to the error when opsys is set to systems
>> >> which use GCC.
>> >
>> > Why the distinction? what bad things will happen if we do this for any
>> > compiler?
>> 
>> Emacs will not install by just running:
>> 
>>       ./configure
>>       make
>>       su
>>       make install
>> 
>> from the distribution.
>
>We are going in circles: as I already said before, Emacs will also not
>install by just running the above if, say, the XPM library is not
>available.