all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: chad <yandros@MIT.EDU>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "emacs-devel@gnu.org Development" <emacs-devel@gnu.org>
Subject: Re: Directory structure changes in Emacs installed on MS-Windows
Date: Fri, 5 Apr 2013 01:48:11 -0700	[thread overview]
Message-ID: <9FE22079-7C57-4F7F-877C-7F6BC0DF7B23@mit.edu> (raw)
In-Reply-To: <83d2u9fr4a.fsf@gnu.org>

On 04 Apr 2013, at 23:06, Eli Zaretskii <eliz@gnu.org> wrote:

> 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.

I don't know if this is helpful to you or not, but the ns port
(--with-ns) features a relocatable tree.  It seems to be implemented
in src/nsterm.m, functions ns_etc_directory(), ns_exec_path(), and
ns_load_path().

~Chad




  reply	other threads:[~2013-04-05  8:48 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 [this message]
2013-04-05  9:18       ` Eli Zaretskii
2013-04-05 13:19     ` Stefan Monnier
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9FE22079-7C57-4F7F-877C-7F6BC0DF7B23@mit.edu \
    --to=yandros@mit.edu \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.