unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Ergus <spacibba@aol.com>
Cc: rms@gnu.org, dmitry@gutov.dev, emacs-devel@gnu.org
Subject: Re: [PATCH] Project out of sources compilation
Date: Thu, 04 Apr 2024 23:16:29 +0300	[thread overview]
Message-ID: <ea27c0fbc6d3dc3329624f15cc117d4a48a2e160.camel@yandex.ru> (raw)
In-Reply-To: <867chd6vgp.fsf@gnu.org>

On Thu, 2024-04-04 at 17:41 +0300, Eli Zaretskii wrote:
> > Date: Thu, 4 Apr 2024 16:27:34 +0200
> > From: Ergus <spacibba@aol.com>
> > Cc: Hi-Angel@yandex.ru, rms@gnu.org, dmitry@gutov.dev,
> > emacs-devel@gnu.org
> > 
> > > The reason is that Emacs's support for "running uininstalled"
> > > assumes
> > > the Lisp files are in the source tree.  IOW, running uninstalled
> > > from
> > > a build directory outside of the source tree does not take the
> > > *.elc
> > > files from that build directory, as I think you can verify if you
> > > look
> > > at the value of load-path.
> > 
> > Exactly, so this is not OOSC and does not behave as expected in
> > OOSC.
> 
> No, it isn't.  Not many programs at all support running uninstalled.
> Emacs does, but only if you build inside the source.  This is
> unrelated to the possibility of out-of-source build, where you are
> supposed to say "make install" after you build.

Indeed running uninstalled is kind of orthogonal to OOSC and may or may
not be supported by a program.  I think this discussion might be
confusing two orthogonal things: α) `.elc` files being put in-tree, and
β) Emacs requiring for them to be put in-tree to run "uninstalled".

For β: I'm sure it's possible to modify Emacs to load `.elc` from the
build dir rather than from the tree.

For α: the lone fact that build artifacts are being put in-tree means
OOSC is not working as expected.

I see what you mean by saying that `configure` and similar files can't
be put into the build dir because that's how autotools work.  Okay. 
But I think this whole discussion about the terminology is becoming not
very useful.  Can we please agree that generating .elc files in the
build dir rather than in tree allows to avoid a number of problems? 
Please note that this has nothing to do with `.elc` files being put in
tarballs, because for that to work you could just build "in-tree" as
usual.  Putting `.elc` files into build dir (which may be in-tree or
out) and allowing Emacs to take those into account is just
simplification in how things work.



  parent reply	other threads:[~2024-04-04 20:16 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4wwljrdnra3bsloehioa46y24ozxajajmvf2elvskxxq3mhtg2.ref@pyv2z5snot6h>
2024-03-16 13:12 ` Project out of sources compilation Ergus
2024-03-16 16:50   ` Konstantin Kharlamov
2024-03-16 19:00     ` Ergus
2024-03-16 20:56       ` Konstantin Kharlamov
2024-03-17  2:53   ` Dmitry Gutov
2024-03-17  7:22     ` Ergus
2024-03-17  8:45       ` Eli Zaretskii
2024-03-17 17:33         ` Ergus
2024-03-17 17:38           ` Eli Zaretskii
2024-03-17 17:58             ` Ergus
2024-03-17 11:36   ` Augusto Stoffel
2024-03-17 17:47     ` Ergus
2024-03-19 18:36       ` Ergus
2024-03-27 16:38         ` [PATCH] " Ergus
2024-03-31  2:41           ` Dmitry Gutov
2024-03-31 21:07             ` Ergus
2024-04-01  7:49               ` Dirk-Jan C. Binnema
2024-04-01 13:52                 ` Ergus
2024-04-01 15:09                   ` Dirk-Jan C. Binnema
2024-04-01 17:18                     ` Ergus
2024-04-02 23:23                   ` Dmitry Gutov
2024-04-03 19:47                     ` Ergus
2024-04-06  2:05                     ` Ergus
2024-04-14  1:44                       ` Dmitry Gutov
2024-04-16 14:56                         ` Ergus
2024-04-22 17:05                         ` Ergus
2024-04-22 18:48                           ` Ergus
2024-04-22 21:20                             ` Mohsin Kaleem
2024-04-23 15:17                               ` Ergus
2024-04-23 19:26                                 ` Mohsin Kaleem
2024-04-26  0:47                               ` Dmitry Gutov
2024-04-02 21:39               ` Richard Stallman
2024-04-02 22:43                 ` Dr. Arne Babenhauserheide
2024-04-05 21:40                   ` Richard Stallman
2024-04-03 10:40                 ` Konstantin Kharlamov
2024-04-03 11:45                   ` Eli Zaretskii
2024-04-03 13:31                     ` Konstantin Kharlamov
2024-04-03 14:11                       ` Eli Zaretskii
2024-04-03 15:00                         ` Konstantin Kharlamov
2024-04-03 15:47                           ` Eli Zaretskii
2024-04-03 17:27                             ` Konstantin Kharlamov
2024-04-03 18:22                               ` Eli Zaretskii
2024-04-03 19:08                                 ` Konstantin Kharlamov
2024-04-03 20:12                                   ` Ergus
2024-04-04  5:26                                     ` Eli Zaretskii
2024-04-04  9:59                                       ` Ergus
2024-04-04 11:59                                         ` Eli Zaretskii
2024-04-04 12:34                                           ` Ergus
2024-04-04 13:02                                             ` Eli Zaretskii
2024-04-04 14:27                                               ` Ergus
2024-04-04 14:41                                                 ` Eli Zaretskii
2024-04-04 18:15                                                   ` Ergus
2024-04-04 18:56                                                     ` Eli Zaretskii
2024-04-04 20:16                                                   ` Konstantin Kharlamov [this message]
2024-04-05  5:11                                                     ` Eli Zaretskii
2024-04-04  5:07                                   ` Eli Zaretskii
     [not found]                               ` <87jzlefgi9.fsf@dick>
2024-04-03 18:44                                 ` Konstantin Kharlamov

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=ea27c0fbc6d3dc3329624f15cc117d4a48a2e160.camel@yandex.ru \
    --to=hi-angel@yandex.ru \
    --cc=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=spacibba@aol.com \
    /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).