unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: emacs-devel@gnu.org
Subject: Sharing native-lisp system load-path between builds
Date: Mon, 26 Jun 2023 03:14:17 +0300	[thread overview]
Message-ID: <871qhzjd0m.fsf@thaodan.de> (raw)


Hey,

I'm building Emacs master for OpenSUSE to provide testing.
OpenSUSE packaging packages Emacs so that they have three builds with
different feature sets: X11 without GTK, GTK and one build just without
X11 or GTK.

This helps different users to chose their preferred builds and keeps
build workers small for Emacs packages build.

The packages share the elisp, native-lisp ahead of time compilations and
docs.

Recently the native-lisp load path changed to change per Emacs
executable. I don't know the exact commit when this changed but it was
between ref 3c8167ec0f9647e6fc33e65b0a0324f96cb795ee and
d46a2fa319808963bbe8d3a90e7dbb13fcd844f5.

Now my questions: Is this a bug or can a different hash be used to
determine the system load-path? It is very useful to precompile the
lisp code once per emacs builds that share the same code.

I tried to bisect when exactly this changed but didn't found the exact
commit.

My package can be found here:
https://build.opensuse.org/package/show/home:Thaodan:emacs/emacs

Thanks, 

Björn Bidar



             reply	other threads:[~2023-06-26  0:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26  0:14 Björn Bidar [this message]
2023-06-26  2:31 ` Sharing native-lisp system load-path between builds Eli Zaretskii
2023-06-26  4:26   ` Björn Bidar
2023-06-26  7:12     ` Andrea Corallo
2023-08-13 23:47       ` Björn Bidar
2023-08-14  2:29         ` Eli Zaretskii
2023-08-14 10:04           ` Björn Bidar
2023-08-14 12:24             ` Eli Zaretskii
     [not found]               ` <87bkf932b5.fsf@thaodan.de>
2023-08-14 18:41                 ` Eli Zaretskii
2023-08-16  7:44                   ` Björn Bidar
2023-08-16  8:49                     ` Andrea Corallo
2023-08-18 22:23                       ` Björn Bidar
2023-08-19  6:21                         ` Eli Zaretskii
2023-09-26 14:26                           ` Sharing native-lisp system load-path between builds, my own error Björn Bidar
2023-06-26 11:18     ` Sharing native-lisp system load-path between builds Eli Zaretskii

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=871qhzjd0m.fsf@thaodan.de \
    --to=bjorn.bidar@thaodan.de \
    --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 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).