unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: emacs-devel@gnu.org
Subject: Re: Installing the Emacs executable
Date: Wed, 24 Apr 2013 20:06:38 +0300	[thread overview]
Message-ID: <83haivx3hd.fsf@gnu.org> (raw)
In-Reply-To: <33A901B8-67E3-4C81-BF5B-7C9B4A8836E1@raeburn.org>

> From: Ken Raeburn <raeburn@raeburn.org>
> Date: Wed, 24 Apr 2013 01:05:07 -0400
> Cc: emacs-devel@gnu.org
> 
> On Apr 19, 2013, at 15:05, Eli Zaretskii <eliz@gnu.org> wrote:
> > That's a different issue.  My question was about what "make install"
> > does with DOC, not what "make emacs" does in src.  We can install DOC
> > under the name DOC-XX.YY.ZZ without changing what happens in src and
> > in etc of the build tree.
> 
> I've long wondered if it would be better to get rid of the DOC file altogether and keep the documentation in the executable image.
> 
> With GCC and ELF systems, it's not that hard to compile the C doc strings into a specially named section

Beware: you might get into the same situation that the Windows build
is today -- you will be unable to strip the resulting executable as
part of "make install-strip", because 'strip' doesn't know anything
about the section you add.

In any case, I thought the tendency was to stay away of tricks that
are too specific to binary formats, to avoid re-living the unexec
problem...



  parent reply	other threads:[~2013-04-24 17:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 16:32 Installing the Emacs executable Eli Zaretskii
2013-04-16 17:15 ` Andreas Schwab
2013-04-16 17:20   ` Glenn Morris
2013-04-16 18:11     ` Eli Zaretskii
2013-04-19 18:29     ` Andreas Schwab
2013-04-19 18:49       ` Eli Zaretskii
2013-04-19 18:57         ` Glenn Morris
2013-04-19 19:05           ` Eli Zaretskii
2013-04-19 19:08             ` Glenn Morris
2013-04-20  1:48               ` Stefan Monnier
2013-04-19 20:58             ` Andreas Schwab
2013-04-20  6:37               ` Eli Zaretskii
2013-04-20 10:44                 ` Andreas Schwab
2013-04-20 10:56                   ` Eli Zaretskii
2013-04-20 11:55                     ` Andreas Schwab
2013-04-20 12:31                       ` Eli Zaretskii
2013-04-20 13:24                         ` Andreas Schwab
2013-04-20 15:43                           ` Eli Zaretskii
2013-04-20 15:56                             ` Andreas Schwab
2013-04-24  5:05             ` Ken Raeburn
2013-04-24 13:12               ` Stefan Monnier
2013-04-24 17:06               ` Eli Zaretskii [this message]
2013-04-24 18:54                 ` Stefan Monnier

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=83haivx3hd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=raeburn@raeburn.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).