all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yasuhiro Kimura <yasu@utahime.org>
Cc: emacs-devel@gnu.org
Subject: Re: Question about native compilation
Date: Wed, 09 Jun 2021 21:21:04 +0300	[thread overview]
Message-ID: <83r1hadhm7.fsf@gnu.org> (raw)
In-Reply-To: <20210610.030102.1585779767359400556.yasu@utahime.org> (message from Yasuhiro Kimura on Thu, 10 Jun 2021 03:01:02 +0900 (JST))

> Date: Thu, 10 Jun 2021 03:01:02 +0900 (JST)
> From: Yasuhiro Kimura <yasu@utahime.org>
> 
> all:
> 	emacs -q -batch -f batch-byte-compile *.el
> .if ${NATIVE_COMPILE} == yes
> 	emacs -q -batch -f batch-native-compile *.el
> .endif

It is better to use "-f batch+native-compile", I think.

> 1. What is the recommended way to check if executable of Emacs
>    supports native compilation?

  emacs -batch --eval "(message \"%s\" system-configuration-features)" | grep NATIVE_COMP

> 2. Is there standard place where 3rd party .eln files should be
>    installed? I expect such directories as
>    ${prefix}/share/emacs/site-lisp or
>    ${prefix}/share/emacs/$(version)/site-lisp for .el and .elc files.

${prefix}/share is for architecture-independent files, so it's the
wrong place.

More importantly: why do you want to install them somewhere? why not
let Emacs compile them when they are first used and store them in
~/.emacs.d/eln-cache?  I think that's the canonical way at the moment.



      parent reply	other threads:[~2021-06-09 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 18:01 Question about native compilation Yasuhiro Kimura
2021-06-09 18:17 ` Stefan Monnier
2021-06-09 18:21 ` Eli Zaretskii [this message]

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

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

  git send-email \
    --in-reply-to=83r1hadhm7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yasu@utahime.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.