[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Packaging Emacs with native compilation enabled
From: |
Bhavin Gandhi |
Subject: |
Re: Packaging Emacs with native compilation enabled |
Date: |
Sun, 5 Dec 2021 23:50:38 +0530 |
On Sun, 5 Dec 2021 at 19:30, Eli Zaretskii <eliz@gnu.org> wrote:
> > 1. Should these files be there in the final package, which is
> > distributed to users?
>
> If you are making a binary distribution (not one where users will have
> to build Emacs from sources), these files should be included, yes.
Thanks! Now I'm able to make sense out of the conversations about
keeping NATIVE_FULL_AOT=1 when building the binary distribution
packages.
> > Based on what I have understood from Andrea's EmacsConf 2021 talk[1] and
> > the "(elisp) Native Compilation" page: the .eln files are CPU specific
> > and should not be shared across.
>
> That's true, but you are already producing Emacs binaries, which are
> necessarily specific to the CPU, right? The *.eln files are just
> shared libraries built for the same architecture as the Emacs binary,
> so they have the same restrictions as the binary.
Understood, that makes sense. And clarifies the following line from the
manual.
> The transportability of natively-compiled code is the same as that of
> shared libraries (‘.so’ or ‘.dll’ files).