[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bloat in the Emacs Windows package
From: |
Eli Zaretskii |
Subject: |
Re: Bloat in the Emacs Windows package |
Date: |
Tue, 23 Apr 2019 08:37:51 +0300 |
> From: address@hidden (Phillip Lord)
> Cc: address@hidden, address@hidden
> Date: Mon, 22 Apr 2019 21:40:39 +0100
>
> >> 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
> >
> > There is no magic: if emacs.exe and emacs-26.2.exe are two separate
> > files (not hard links to the same file data), then yes, you will need
> > the additional commands above. Sorry for not saying that explicitly.
>
> >From what you are saying, emacs.exe and emacs-26.2.exe *will be* hard
> links before they are zipped, but not after.
If they are hard links before the above commands, you don't need
separate commands for each executable. When unzipped, they will both
have the same debuglink section.
- Re: Bloat in the Emacs Windows package, (continued)
- Re: Bloat in the Emacs Windows package, Phillip Lord, 2019/04/22
- Re: Bloat in the Emacs Windows package, Stefan Monnier, 2019/04/22
- Re: Bloat in the Emacs Windows package, Phillip Lord, 2019/04/23
- Re: Bloat in the Emacs Windows package, Robert Pluim, 2019/04/23
- Re: Bloat in the Emacs Windows package, Phillip Lord, 2019/04/23
- Re: Bloat in the Emacs Windows package, Phillip Lord, 2019/04/26
- Re: Bloat in the Emacs Windows package, Óscar Fuentes, 2019/04/26
- Re: Bloat in the Emacs Windows package, Phillip Lord, 2019/04/26
- Re: Bloat in the Emacs Windows package, Björn Lindqvist, 2019/04/27
- Re: Bloat in the Emacs Windows package, Phillip Lord, 2019/04/27
- Re: Bloat in the Emacs Windows package,
Eli Zaretskii <=
Re: Bloat in the Emacs Windows package, Phillip Lord, 2019/04/17