unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: akrl@sdf.org
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: Building a tarball with native-compilation support
Date: Sat, 07 Aug 2021 09:48:13 +0300	[thread overview]
Message-ID: <838s1diwcy.fsf@gnu.org> (raw)
In-Reply-To: <83bl69ixht.fsf@gnu.org> (message from Eli Zaretskii on Sat, 07 Aug 2021 09:23:42 +0300)

> Date: Sat, 07 Aug 2021 09:23:42 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: larsi@gnus.org, emacs-devel@gnu.org
> 
> So I think a better way would be to write a function in Emacs Lisp
> that is passed a list of preloaded Lisp files, and natively-compiles
> those of them whose *.eln files are either outdated or do not exist.

Actually, such a function already exists: native-compile-async.  We
just need to write a suitable function to act as the SELECTOR for it.



  reply	other threads:[~2021-08-07  6:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05  6:25 Building a tarball with native-compilation support Eli Zaretskii
2021-08-05 21:55 ` Andrea Corallo via Emacs development discussions.
2021-08-06  6:05   ` Eli Zaretskii
2021-08-06 14:37     ` Stefan Monnier
2021-08-06 17:41       ` Eli Zaretskii
2021-08-07 13:28         ` Stefan Monnier
2021-08-07 13:35           ` Eli Zaretskii
2021-08-07  6:23     ` Eli Zaretskii
2021-08-07  6:48       ` Eli Zaretskii [this message]
2021-08-07 10:32         ` Eli Zaretskii
2021-08-14  7:44           ` Eli Zaretskii
2021-08-17 10:16             ` Andrea Corallo via Emacs development discussions.
2021-08-17 11:44               ` Eli Zaretskii
2021-08-17 21:49                 ` Andrea Corallo via Emacs development discussions.
2021-08-18 13:17                   ` Eli Zaretskii
2021-08-18 15:03                     ` Andrea Corallo via Emacs development discussions.
2021-08-26 13:42                     ` Eli Zaretskii
2021-08-27 13: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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=838s1diwcy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=akrl@sdf.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).