Le lun. 11 mai 2020 à 18:20, Eli Zaretskii <
eliz@gnu.org> a écrit :
> From: Nicolas Bértolo <nicolasbertolo@gmail.com>
> Date: Mon, 11 May 2020 12:20:36 -0300
> Cc: Andrea Corallo <akrl@sdf.org>, emacs-devel@gnu.org
>
> > I don't think it would be wise for us to distribute libgccjit, because
> > then we'd need to distribute the GCC sources, and the user will be
> > unable to reliably use the shipped libgccjit with their local GCC
> > installation (due to possible version mismatch).
>
> IMHO that is really inconvenient from the point of view of a user that just
> wants to install Emacs and use all its features.
This is a price to pay for compiling to native code using an external
compiler. there's no way around this, I think. People who cannot
afford installing a working compiler and Binutils will have to give up
compiling Lisp files to native code (the Lisp files that come with
Emacs can still be provided as *.eln, I would hope).
<Out_of_Topic>
I guess I am not alone reading this and thinking:
well, Common Lisp provides an embedded compiler even at runtime for years.
(Sorry but could not resist)
About the issue there. In the Windows context I would totally follow Nicolas here.
If Emacs users have to install a working gcc toolchain to be able to compile to native code,
it almost totally defeats the purpose.
IMHO, the right way to do it is to target a binary distribution that has all of what is needed.
Else, you will end up in a situation where people must compile their own binary.
Nobody will do it.
Best regards,
Fabrice