From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: bug-guile@gnu.org
Subject: Re: guile-snarf writes to $srcdir, which is not kosher
Date: Mon, 08 Apr 2002 12:34:52 -0700 [thread overview]
Message-ID: <E16ueui-0001b7-00@giblet> (raw)
In-Reply-To: <873cy6f8av.fsf@zagadka.ping.de> (message from Marius Vollmer on 08 Apr 2002 18:45:44 +0200)
From: Marius Vollmer <mvo@zagadka.ping.de>
Date: 08 Apr 2002 18:45:44 +0200
A VPATH build is when you compile in a directory other than the source
directory. This is useful when you want to compile a package for
different configurations but from a common source. The name stems
from the fact that it is implemented using the VPATH variable of make.
could you describe VPATH as "configure in place, make from elsewhere"?
or is configure done elsewhere also? i've heard the latter referred to
as srcdir!=builddir (and usually make is done where configure is).
> if you remove cleaning you need to promote SCM_MAGIC_SNARFER to required
> status and document accordingly.
It is already.
all i see is this:
During snarfing, the pre-processor macro @code{SCM_MAGIC_SNARFER} is
defined.
i'm assuming that whatever changes made to branch_release-1-6 that are
long-term applicable would be also made in HEAD roughly concurrently,
but i guess this is saved for later?
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-04-08 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-07 22:55 guile-snarf writes to $srcdir, which is not kosher Marius Vollmer
2002-04-08 2:35 ` Thien-Thi Nguyen
2002-04-08 16:45 ` Marius Vollmer
2002-04-08 19:34 ` Thien-Thi Nguyen [this message]
2002-04-09 17:03 ` Marius Vollmer
2002-04-22 7:58 ` Thien-Thi Nguyen
2002-04-10 21:10 ` Rob Browning
2002-04-23 21:16 ` Thien-Thi Nguyen
2002-04-23 22:42 ` Rob Browning
2002-04-23 22:50 ` Thien-Thi Nguyen
2002-04-23 23:09 ` Rob Browning
2002-04-23 23:51 ` Thien-Thi Nguyen
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E16ueui-0001b7-00@giblet \
--to=ttn@giblet.glug.org \
--cc=bug-guile@gnu.org \
--cc=ttn@glug.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).