unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mekeor Melire <mekeor@posteo.de>
To: 64586@debbugs.gnu.org
Cc: Liliana Marie Prikler <liliana.prikler@gmail.com>,
	Andrew Tropin <andrew@trop.in>
Subject: bug#64586: Emacs-Packages should contain native-compiled files
Date: Wed, 12 Jul 2023 18:19:12 +0000	[thread overview]
Message-ID: <875y6pgdnn.fsf@posteo.de> (raw)

Emacs can interpret/load at least four kinds of source files. 
Listed with increasing performance:

- Emacs-Lisp source code: *.el
- Byte-compiled Emacs-Lisp: *.elc
- Native-compiled Emacs-Lisp: *.eln
- Shared-object files: *.so

Guix installs el- and elc-files into ~/.guix-profile/share/emacs/site-lisp which is added to the 
environment-variable EMACSLOADPATH. eln-files are installed into 
~/.guix-profile/lib/emacs/native-site-lisp which is added to 
EMACSNATIVELOADPATH. For Emacs-related so-files, Guix currently 
does not have any convention; see 
<https://issues.guix.gnu.org/63987>.

If I understand correctly, it is only the following Emacs-packages that ship with eln-files when installed with Guix, because they specify `#:emacs ,emacs` in the package declaration, so that native-compilation is available during build-time which is used if it's available: https://git.savannah.gnu.org/cgit/guix.git/tree/guix/build/emacs-utils.scm?h=6d0b3684628fe24555055d4a97d703a1b0b59660#n144

    emacs-auctex
    emacs-citeproc-el
    emacs-zig-mode
    emacs-flycheck-grammalecte
    emacs-sudo-edit
    emacs-elquery
    emacs-cov
    emacs-pos-tip
    emacs-posframe
    emacs-xelb
    emacs-exwm
    emacs-xelb-no-x-toolkit
    emacs-exwm-no-x-toolkit
    emacs-exwm-x
    emacs-jabber
    emacs-ement
    emacs-circe
    emacs-esxml
    emacs-nov-el
    emacs-wordgen
    emacs-picpocket
    emacs-lsp-mode
    emacs-jsdoc
    emacs-tramp
    emacs-elpher
    emacs-telega

So, if my understanding is correct, and assuming that we want to ship eln-files, Emacs-packages should all be built with a package of Emacs that supports native-compilation.




             reply	other threads:[~2023-07-12 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 18:19 Mekeor Melire [this message]
2023-07-12 19:36 ` bug#64586: Emacs-Packages should contain native-compiled files Liliana Marie Prikler
2023-08-23 15:37   ` Simon Tournier
2023-08-23 18:36     ` Liliana Marie Prikler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875y6pgdnn.fsf@posteo.de \
    --to=mekeor@posteo.de \
    --cc=64586@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=liliana.prikler@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).