all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: emacs-devel@gnu.org
Subject: origin/features/native-comp: Where do jitted .eln files  go?
Date: Mon, 24 Aug 2020 12:52:14 -0700	[thread overview]
Message-ID: <p91lfi36cup.fsf@google.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 736 bytes --]


Hi Andrea and others on the native-branch:

I successfully built the native-comp branch and ran it --- as elisp libs
get loaded from my elpa/ directory etc, I see  Emacs saying that it's
native compiling those files -- however I have no idea where it places
those (I can see the .eln files in my Emacs build for the .el files that
come with Emacs).

Additional question: If I wanted to native-compile a given elisp
package, what elisp function should I call to do the native compile?

Finally: It wasn't obvious that doing the native compile requireds the
--with-zip flag to configure.

Thanks Andrea for the awesome work to get the native-comp branch to such
a mature state!
-- 
7©4Id: kg:/m/0285kf1  •0Ü87©4



             reply	other threads:[~2020-08-24 19:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 19:52 T.V Raman [this message]
2020-08-25  6:18 ` origin/features/native-comp: Where do jitted .eln files go? Andrea Corallo via Emacs development discussions.
2020-08-25 15:23   ` Possible Race condition? " T.V Raman
2020-08-25 19:53     ` Andrea Corallo via Emacs development discussions.
2020-08-25 20:19       ` T.V Raman
2020-08-25 21:04         ` Andrea Corallo via Emacs development discussions.
     [not found]   ` <24394.59245.98750.79288@google.com>
     [not found]     ` <xjf8sdwzjov.fsf@sdf.org>
2020-08-30 14:07       ` T.V Raman
2020-08-30 20:33         ` Andrea Corallo via Emacs development discussions.

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=p91lfi36cup.fsf@google.com \
    --to=raman@google.com \
    --cc=emacs-devel@gnu.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.