unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: Building Emacs out of source tree?
Date: Sun, 17 Mar 2024 20:33:45 +0100	[thread overview]
Message-ID: <ZfdFmYKA1iRr0Cnb@tuxteam.de> (raw)
In-Reply-To: <0091d885-6904-475a-8e46-956756cf0057@starynkevitch.net>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

On Sun, Mar 17, 2024 at 06:53:59PM +0100, Basile Starynkevitch wrote:
> 
> On 3/17/24 15:18, Eli Zaretskii wrote:

[...]

> I actually am git pulling and buiding GNU emacs on Linux Debian/x86-64 
> (inside its source tree) more than twice a week.

Thanks for one more (or actually many more :) data points!

As I wrote, it works for me in-tree, too.

> (Why do you want to build it outside of source tree?)

Back then (TM), when you built off a tarball, there was
a positive advantage to this. Nowadays, with git, it has
lost much of its importance.

Oldtimer habits,if you will.

That was my original post's intention, to find out whether
Emacs still cares about out-of-tree builds. Had the answer
been "no", I'd changed that habit, but I understood Eli's
answer as "yes", so I'll try to find out :-)

> Very often it build and works ok.

Some time ago I have been doing that, and my experience was
like yours, yes.

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2024-03-17 19:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-17 12:54 Building Emacs out of source tree? tomas
2024-03-17 14:18 ` Eli Zaretskii
2024-03-17 17:53   ` Basile Starynkevitch
2024-03-17 19:33     ` tomas [this message]
2024-03-17 19:24   ` tomas
2024-03-18  8:25     ` Robert Pluim
2024-03-18  8:50       ` tomas
2024-03-18 13:27       ` Eli Zaretskii
2024-03-18 13:59         ` tomas
2024-03-19  6:18 ` Andreas Röhler
2024-03-20  5:41 ` SOLVED [was: Building Emacs out of source tree?] tomas

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=ZfdFmYKA1iRr0Cnb@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=basile@starynkevitch.net \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).