all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Glenn Morris <rgm@gnu.org>
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:20:31 -0400	[thread overview]
Message-ID: <jwva9c8wyhk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <bg38i04wrc.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 29 Mar 2014 15:42:31 -0400")

>>> It's not important, but I wondered if anyone had an idea for a solution?
>> I'd guess the solution is to introduce a build-specific lisp directory,
>> alongside ${archlibdir}.
> Yes, but what would it even be called?
> It's name would depend on the specific configure options used. Yuck.
> So I guess the idea doesn't work. Oh well.

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)?

Of course, if this src/config.el is where source-directory is defined,
we'll need to pass the /foo/src/config.el name from src/Makefile to
the temacs process on the command line.


        Stefan



  reply	other threads:[~2014-03-29 20:20 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 [this message]
2014-03-29 20:40       ` Glenn Morris
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

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

  git send-email \
    --in-reply-to=jwva9c8wyhk.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@gnu.org \
    --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 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.