unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Daniel Colascione <dancol@dancol.org>, Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Handling of links with portable dumper
Date: Sun, 7 Apr 2019 10:44:16 -0700	[thread overview]
Message-ID: <fb285b84-bdea-0881-b99f-0654402c0f57@cs.ucla.edu> (raw)
In-Reply-To: <17ec5b0b6f1f86796561ff9a40612068.squirrel@dancol.org>

Daniel Colascione wrote:
> Paul, is there something in
> gnulib I can just link to?

Sorry, I've lost context. What function do you want? canonicalize_file_name? 
set_program_name_and_installdir? I'm not a big fan of the latter, as it's a 
portability heavyweight (it makes lots of assumptions and might not be 
applicable to Emacs).

I still think it'd be better to put the dump into the executable itself, which 
can be done portably simply by linking a big C character array into the 
executable. in the long run this will be better for users (and for us) than 
fiddling with portability minefields like set_program_name_and_installdir.



  reply	other threads:[~2019-04-07 17:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 22:39 Handling of links with portable dumper Richard Stallman
2019-04-05  5:42 ` Eli Zaretskii
2019-04-05 22:32   ` Richard Stallman
2019-04-06  6:30     ` Eli Zaretskii
2019-04-06 23:24       ` Richard Stallman
2019-04-07  2:41         ` Eli Zaretskii
2019-04-07 17:04           ` Daniel Colascione
2019-04-07 17:44             ` Paul Eggert [this message]
2019-04-07 22:07               ` Clément Pit-Claudel
2019-04-08  4:04                 ` Michael Welsh Duggan
2019-04-08  4:08                   ` Paul Eggert
2019-04-07 18:15             ` Eli Zaretskii
2019-04-08 22:00             ` Richard Stallman
2019-04-06 22:29     ` Stefan Monnier
2019-04-07 21:58       ` Richard Stallman

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=fb285b84-bdea-0881-b99f-0654402c0f57@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=dancol@dancol.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).