From: Mathias Dahl <mathias.dahl@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: How can I put together a small bare bones "Emacs for scripting" package?
Date: Sat, 25 Jan 2020 21:12:04 +0100 [thread overview]
Message-ID: <CABrcCQ4Ppzm244CZ+iqs+fy7BcuXvPYHP-vUs8os9kunJmBxZw@mail.gmail.com> (raw)
In-Reply-To: <83blqsq8yb.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
>
> > One thing that I noticed is the HUGE difference in size of the exe file
> between Emacs 24 and later versions. I
> > listed the sizes of the folder when I keep my different Emacs versions:
> >
> > 8.8M ./emacs-24.5-official/bin/emacs.exe
> > 91M ./emacs-25.1-2-x86_64-w64-mingw32_2016_11_16/bin/emacs.exe
> > 119M ./emacs-26.1-x86_64/bin/emacs.exe
> > 120M ./emacs-26.2-x86_64/bin/emacs.exe
> > 130M ./emacs-26.3-x86_64/bin/emacs.exe
> > 16M ./emacs-bin-w64-24.4/emacs/bin/emacs.exe
> > 121M ./emax64-bin-20180529/emax64/bin/emacs.exe
> > 119M ./old/emacs-26.1/bin/emacs.exe
>
> The small ones are stripped, the large ones are with debug info. If
> you have the 'strip' command (from Binutils) installed, you can strip
> the large ones as well.
>
Ah, makes sense.
I tried three different versions of MingW and binutils/strip until I found
one that did not fail :)
Now I have an emacs.exe (emacs-26.3-x86_64-no-deps, from the official Gnu
download location) that is 30 MB in size instead of 132 MB :) And, it still
seems
to work.
Thanks a lot!
/Mathias
[-- Attachment #2: Type: text/html, Size: 1526 bytes --]
next prev parent reply other threads:[~2020-01-25 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 15:34 How can I put together a small bare bones "Emacs for scripting" package? Mathias Dahl
2020-01-24 15:49 ` Eli Zaretskii
2020-01-24 16:18 ` Eli Zaretskii
2020-01-24 21:37 ` Mathias Dahl
2020-01-25 7:41 ` Eli Zaretskii
2020-01-25 20:12 ` Mathias Dahl [this message]
2020-01-27 14:36 ` Mathias Dahl
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=CABrcCQ4Ppzm244CZ+iqs+fy7BcuXvPYHP-vUs8os9kunJmBxZw@mail.gmail.com \
--to=mathias.dahl@gmail.com \
--cc=eliz@gnu.org \
--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.