From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: limit native compilation - how
Date: Sun, 16 Jan 2022 19:09:35 +0100 [thread overview]
Message-ID: <864k637dsw.fsf@duenenhof-wilhelm.de> (raw)
In-Reply-To: <86sftn1ucj.fsf@gmail.com> (Andy Moreton's message of "Sun, 16 Jan 2022 17:08:44 +0000")
Andy Moreton <andrewjmoreton@gmail.com> writes:
> On Sun 16 Jan 2022, H. Dieter Wilhelm wrote:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
>>>> Cc: help-gnu-emacs@gnu.org
>>>> Date: Sun, 16 Jan 2022 13:01:37 +0100
>>>>
>>>> Could the difference in size result from opening my Emacs, I think I
>>>> checked Emacs-28.0.91 on the machine 106MB? On machine 55MB I didn't
>>>> run Emacs yet.
>>>
>>> The contents of the native-lisp/ directory doesn't change once Emacs
>>> is built.
>>
>> Really, please see below, could it be you meant perhaps the preloaded/
>> folder? (Just guessing.)
>>
>>> If you cannot figure this out, compare the contents of the two
>>> native-lisp/ directories.
>>
>> machine 105 MB:
>> |- native-lisp/
>> |- 28.0.91-59ee6325/
>> | |- Some .eln files
>> | |- preloaded/
>> | | 45 MB .eln
>> |- 28.0.91-aa40abb8/
>> | Some other .eln files
>> |- preloaded/
>> |- 45 Mb .eln files
>
> This shows native builds for two emacs versions with different native
> compilation hash signatures (which are used to ensure that the .eln
> DLLs are compatible with the emacs executable that they are loaded
> into).
As far as I remember, I updated with pacman - after the first
compilation - the MSYS/MinGW toolchain and wanted to see if it would
make a difference to the native compilation.
> The variable `comp-native-version-dir' contains the matching name for a
> running emacs with native comilation support.
I see, thank you for the information!
Dieter
--
Best wishes
H. Dieter Wilhelm
Zwingenberg, Germany
next prev parent reply other threads:[~2022-01-16 18:09 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 15:42 limit native compilation - how Colin Baxter 😺
2022-01-15 15:58 ` Eli Zaretskii
2022-01-15 16:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 16:38 ` Eli Zaretskii
2022-01-15 16:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 17:55 ` Eli Zaretskii
2022-01-15 18:58 ` Colin Baxter 😺
2022-01-15 19:12 ` Eli Zaretskii
2022-01-15 19:21 ` H. Dieter Wilhelm
2022-01-15 20:31 ` Colin Baxter 😺
2022-01-15 22:15 ` H. Dieter Wilhelm
2022-01-16 7:13 ` Eli Zaretskii
2022-01-16 7:15 ` Eli Zaretskii
2022-01-16 7:41 ` Colin Baxter 😺
2022-01-16 9:26 ` Eli Zaretskii
2022-01-17 19:37 ` H. Dieter Wilhelm
2022-01-17 20:39 ` Colin Baxter 😺
2022-01-16 8:39 ` Eli Zaretskii
2022-01-16 11:30 ` H. Dieter Wilhelm
2022-01-16 11:42 ` Eli Zaretskii
2022-01-16 12:01 ` H. Dieter Wilhelm
2022-01-16 12:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 12:17 ` Eli Zaretskii
2022-01-16 13:24 ` H. Dieter Wilhelm
2022-01-16 13:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 13:52 ` H. Dieter Wilhelm
2022-01-16 13:59 ` Eli Zaretskii
2022-01-16 18:37 ` H. Dieter Wilhelm
2022-01-16 18:46 ` Eli Zaretskii
2022-01-17 13:38 ` H. Dieter Wilhelm
2022-01-17 13:49 ` Eli Zaretskii
2022-01-17 16:11 ` H. Dieter Wilhelm
2022-01-17 16:30 ` Corwin Brust
2022-01-17 19:03 ` H. Dieter Wilhelm
2022-01-17 19:23 ` Corwin Brust
2022-01-17 21:54 ` Corwin Brust
2022-01-18 14:34 ` Eli Zaretskii
2022-01-18 19:04 ` H. Dieter Wilhelm
2022-01-17 16:55 ` Eli Zaretskii
2022-01-18 2:57 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-18 3:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 21:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 21:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 22:10 ` Michael Heerdegen
2022-01-16 13:48 ` Eli Zaretskii
2022-01-16 17:08 ` Andy Moreton
2022-01-16 18:09 ` H. Dieter Wilhelm [this message]
2022-01-15 17:55 ` Colin Baxter 😺
2022-01-15 16:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=864k637dsw.fsf@duenenhof-wilhelm.de \
--to=dieter@duenenhof-wilhelm.de \
--cc=andrewjmoreton@gmail.com \
--cc=help-gnu-emacs@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.
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).