Re: On elisp running native

[Eli Zaretskii]

> From: Andrea Corallo <address@hidden>
> Date: Wed, 01 Jan 2020 18:42:02 +0000
> Cc: Eli Zaretskii <address@hidden>, address@hidden
> 
> Stefan Monnier <address@hidden> writes:
> 
> > I think the focus should be on:
> > - making it work everywhere
> > - making it easy/convenient to use (e.g. even if you share your $HOME 
> > between
> >   different architectures or even different OSes as well as different
> >   versions of Emacs)
> 
> I think the natural action would be to move the eln in the build
> directory (as these are in fact compiled).  Unfortunately this would not
> work with the elpa packages...  The other option would be to add a
> suffix to the the eln file but is not nice at all.  Any idea?

It might help to look at what Guile does when installing the *.go
files, and also how it handles the JIT compilation of the *.scm
files.  AFAIU, the *.go files are also architecture-specific.  Note
that Guile also has cache directories, both system-wide and per-user,
to support JIT compilation.  This could give some ideas.