unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stephen Leake <stephen_leake@member.fsf.org>, emacs-devel@gnu.org
Subject: Re: Directory structure changes in Emacs installed on MS-Windows
Date: Fri, 05 Apr 2013 09:19:21 -0400	[thread overview]
Message-ID: <jwvd2u986br.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83d2u9fr4a.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 05 Apr 2013 09:06:45 +0300")

> It would be important if it were true, but I don't think it's true.
> The way epaths.h is generated from epaths.in on Posix platforms leaves
> the root of the Emacs installation tree (specified via --prefix)
> hard-coded into the binary, and Emacs (AFAIK) currently doesn't
> support relocation of the installation tree on Posix systems.
> By contrast, on Windows relocation is a matter of routine.  So I cannot
> use the epaths-force target of the top-level Makefile anyway.

FWIW, such a relocation issue came up with the NS port, and as
I pointed out back then, it would be better to do it once and for all
uniformly, i.e. also do that relocation for posix platforms.


        Stefan



  parent reply	other threads:[~2013-04-05 13:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 17:45 Directory structure changes in Emacs installed on MS-Windows Eli Zaretskii
2013-04-04 22:51 ` Xue Fuqiao
2013-04-04 23:03 ` Stephen Leake
2013-04-05  6:06   ` Eli Zaretskii
2013-04-05  8:48     ` chad
2013-04-05  9:18       ` Eli Zaretskii
2013-04-05 13:19     ` Stefan Monnier [this message]
2013-04-05 14:18       ` Eli Zaretskii
2013-04-05 15:19         ` Stefan Monnier
2013-04-05 15:20         ` Glenn Morris
2013-04-05 17:32           ` chad
2013-04-04 23:16 ` Andy Moreton
2013-04-05  6:08   ` Eli Zaretskii

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=jwvd2u986br.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@member.fsf.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).