emacs-devel
[Top][All Lists]
Advanced

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

Re: Android port


From: Eli Zaretskii
Subject: Re: Android port
Date: Sat, 05 Aug 2023 09:39:23 +0300

> From: Po Lu <luangruo@yahoo.com>
> Cc: angelo.g0@libero.it,  emacs-devel@gnu.org
> Date: Sat, 05 Aug 2023 08:48:33 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > When why is asprintf.c being compiled, if its module is disabled?
> 
> Because the Gnulib configury includes it within LIBOBJ:
> 
> AC_DEFUN([gl_REPLACE_VASPRINTF],
> [
>   AC_LIBOBJ([vasprintf])
>   AC_LIBOBJ([asprintf])
>   AC_REQUIRE([gl_STDIO_H_DEFAULTS])
> 
> whenever it detects that asprintf isn't present on the host system.

What is gl_REPLACE_VASPRINTF, and why is it set for MinGW?  Can that
be disabled somehow (without setting configure variables that test
specific features)?

> > Disabling a module should disable the lib/Makefile rules that compile
> > the module.
> 
> Gnulib doesn't support disabling these modules through Makefile options.

Then we should ask them to add that, or help us solve this in another
proper way.

Paul and Bruno, can you please advise how to resolve this issue?  We
need to disable the compilation of these *printf modules on
MS-Windows, since the Windows build doesn't need them, and compiling
them causes compile-time errors.  The usual method of omitting a
module, like we do in nt/gnulib-cfg.mk, seems not to work in the above
case for some reason.

Another possible way forward is for Gnulib to modify asprintf.c so
that it does compile with MinGW (and then it will be left unused on
Windows in libgnu.a).

TIA



reply via email to

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