unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
Subject: Re: build-specific lisp files (generated by configure)
Date: Sat, 29 Mar 2014 16:40:10 -0400	[thread overview]
Message-ID: <n3vbuwvivp.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwva9c8wyhk.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 29 Mar 2014 16:20:31 -0400")

Stefan Monnier wrote:

> I'm not sure I completely understand the issue, but could we generate
> the file in src/config.el and then from loadup.el load it via
> (expand-file-name "src/config.el" source-directory)?

Sure, but that's not really the problem.

The problem is installed CANNOT_DUMP builds where the source has been
deleted. For them, we'd have to install config.el somewhere. And where
would it go? It would have to be a build-specific location.

Not that we really support CANNOT_DUMP builds anyway (pretty sure I
accidentally broke the Makefiles for those a while ago).

Anyway, it's not important, since there's no need to make such a change.



  reply	other threads:[~2014-03-29 20:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-29  3:09 build-specific lisp files (generated by configure) Glenn Morris
2014-03-29  8:39 ` Andreas Schwab
2014-03-29 19:42   ` Glenn Morris
2014-03-29 20:20     ` Stefan Monnier
2014-03-29 20:40       ` Glenn Morris [this message]
2014-03-29 21:13     ` Andreas Schwab
2014-03-29 21:17       ` Glenn Morris
2014-03-29 22:05         ` Andreas Schwab
2014-03-29 22:11           ` Glenn Morris
2014-03-29 22:17             ` Andreas Schwab
2014-03-29 22:32               ` Glenn Morris
2014-03-29 22:51                 ` Andreas Schwab
2014-03-29 22:58                   ` Glenn Morris

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=n3vbuwvivp.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=schwab@linux-m68k.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).