unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: bjourne@gmail.com, emacs-devel@gnu.org
Subject: Re: Bloat in the Emacs Windows package
Date: Thu, 18 Apr 2019 22:19:26 +0100	[thread overview]
Message-ID: <87a7gnypsx.fsf@russet.org.uk> (raw)
In-Reply-To: <83v9zbcesn.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Apr 2019 22:08:08 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Phillip Lord <phillip.lord@russet.org.uk>
>> Cc: bjourne@gmail.com,  emacs-devel@gnu.org
>> Date: Thu, 18 Apr 2019 17:05:14 +0100
>> 
>> > I can tell how to do the latter, if you want.  It boils down to
>> > running 2 objcopy commands.
>> 
>> So many options!
>> 
>> Again, happy to do whatever can be fitted into my shell script that I
>> use to build the zip files.
>
> Not sure if that's a yes, but anyway...
>
> Given an unstripped emacs.exe, you produce the stripped emacs.exe and
> the separate debug info file like this:
>
>   objcopy --only-keep-debug emacs.exe emacs.debug
>   strip -g emacs.exe
>   objcopy --add-gnu-debuglink=emacs.debug emacs.exe
>
> When unpacked, the emacs.debug file should install into the bin/.debug
> directory of the Emacs installation.

Would this impact on emacs-26.2.exe also or would I need to things like:

objcopy --only-keep-debug emacs.exe emacs.debug
strip -g emacs.exe
strip -g emacs-26.2.exe
objcopy --add-gnu-debuglink=emacs.debug emacs.exe
objcopy --add-gnu-debuglink=emacs.debug emacs-26.2.exe




To summarise my feelings about the thread so far:

 - I think most normal users don't need debug symbols, so I would be
   minded to remove them (or not put them). I don't know why I have
   added "-g3" to the default options. People who know what to do with
   debug symbols are likely to be able to build Emacs for
   themselves.

 - We currently install emacs.exe and emacs-26.2.exe. I think we should
   continue doing this because it is how we do it on other
   platforms. The disk space requirement is small (and will be smaller
   if  we remove debug symbols). It probably adds little to the
   download bandwith (because of zip) and will add nothing with the .exe
   installer for Emacs-27. And NTFS compression fixes the problem (and
   more) for those who really care about space (and they are probably
   using it already).

I am happy to be corrected here if I am missing some unintended
consequence, or if you disagree with my justifications.


Unanswered questions for me:

 - If we remove debug symbols, why not do -O3 which may produce some
   performance benefit?
 - Is it better to do "-g0" which I believe stops adding debug symbols,
   or switch "make install" for "make install-strip"?


Doing any of these things (adding -O3, -g0 or using make install-strip)
are trivial to implement and cost me nothing in ongoing maintenance.

Phil


 








  reply	other threads:[~2019-04-18 21:19 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17  5:01 Bloat in the Emacs Windows package Björn Lindqvist
2019-04-17  7:31 ` Eli Zaretskii
2019-04-17 11:15   ` Van L
2019-04-17 11:26     ` Eli Zaretskii
2019-04-17 12:39   ` Stefan Monnier
2019-04-17 14:49     ` Eli Zaretskii
2019-04-17 16:17       ` Eli Zaretskii
2019-04-18 22:02         ` Björn Lindqvist
2019-04-19  7:00           ` Eli Zaretskii
2019-04-17 17:26     ` Phillip Lord
2019-04-17 17:55       ` Stefan Monnier
2019-04-19  0:02       ` Björn Lindqvist
2019-04-19  7:33         ` Eli Zaretskii
2019-04-19 13:23           ` Óscar Fuentes
2019-04-22 21:04             ` Phillip Lord
2019-04-22 21:41               ` Óscar Fuentes
2019-04-17 13:42   ` Stefan Monnier
2019-04-17 16:19     ` Óscar Fuentes
2019-04-17 17:28     ` Phillip Lord
2019-04-17 15:07   ` Björn Lindqvist
2019-04-17 16:32     ` Eli Zaretskii
2019-04-18 23:44       ` Björn Lindqvist
2019-04-19  7:27         ` Eli Zaretskii
2019-04-19 14:17           ` Óscar Fuentes
2019-04-19 15:05             ` Eli Zaretskii
2019-04-22 20:55             ` Phillip Lord
2019-04-17 17:39     ` Phillip Lord
2019-04-17 18:06       ` Stefan Monnier
2019-04-17 18:32       ` Eli Zaretskii
2019-04-18 16:05         ` Phillip Lord
2019-04-18 19:08           ` Eli Zaretskii
2019-04-18 21:19             ` Phillip Lord [this message]
2019-04-18 23:12               ` Óscar Fuentes
2019-04-19  6:29               ` Eli Zaretskii
2019-04-22 20:40                 ` Phillip Lord
2019-04-23  2:25                   ` Stefan Monnier
2019-04-23 10:01                     ` Phillip Lord
2019-04-23 11:28                       ` Robert Pluim
2019-04-23 21:49                         ` Phillip Lord
2019-04-26 16:30                       ` Phillip Lord
2019-04-26 17:04                         ` Óscar Fuentes
2019-04-26 21:41                           ` Phillip Lord
2019-04-27 18:12                         ` Björn Lindqvist
2019-04-27 18:17                           ` Phillip Lord
2019-05-03  1:06                             ` Björn Lindqvist
2019-05-03  6:49                               ` Eli Zaretskii
2019-05-03 18:38                                 ` Björn Lindqvist
2019-05-03 18:42                                   ` Eli Zaretskii
2019-05-03 20:20                                     ` Stefan Monnier
2019-04-23  5:37                   ` Eli Zaretskii
2019-04-17 15:44 ` Phillip Lord
2019-04-17 16:25   ` Óscar Fuentes
2019-04-17 16:46     ` Eli Zaretskii
2019-04-18 16:00       ` Phillip Lord
2019-04-18 15:56     ` Phillip Lord
2019-04-18 16:39       ` Óscar Fuentes

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=87a7gnypsx.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=bjourne@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 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).