After the changes in Update 11
to gccemacs, the native *.eln files are cached with a hash. This hash seems to
be in part based on the absolute file path of the lisp file in question. As
Emacs.app is self-contained, the absolute path at build time and will not be the
same as once it's installed into /Applications.
This means that all the natively compiled *.eln files bundled into Emacs.app
will not be used, and instead all lisp sources will be natively compiled and
cached in the the user cache (~/.emacs.d/eln-cache/ by default). Native
compilation status can be viewed in the *Async-native-compile-log* buffer.
Because of this, NATIVE_FAST_BOOT is enabled by default ensuring as fast a
build as possible, with as little native compilation as possible at build time.
jimeh
commented
4 years ago
After the changes in Update 11 to gccemacs, the native
*.elnfiles are cached with a hash. This hash seems to be in part based on the absolute file path of the lisp file in question. As Emacs.app is self-contained, the absolute path at build time and will not be the same as once it's installed into/Applications.This means that all the natively compiled
*.elnfiles bundled into Emacs.app will not be used, and instead all lisp sources will be natively compiled and cached in the the user cache (~/.emacs.d/eln-cache/by default). Native compilation status can be viewed in the*Async-native-compile-log*buffer.Because of this,
NATIVE_FAST_BOOTis enabled by default ensuring as fast a build as possible, with as little native compilation as possible at build time.