From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: bug-guile@gnu.org
Subject: Re: guile-snarf writes to $srcdir, which is not kosher
Date: 08 Apr 2002 18:45:44 +0200 [thread overview]
Message-ID: <873cy6f8av.fsf@zagadka.ping.de> (raw)
In-Reply-To: <E16uOzo-0000eb-00@giblet>
Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
> what is a "VPATH build", specifically?
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.
> what other kinds of builds are there?
I only about VPATH builds and 'normal' builds where the object files
end up in the same directory as the source.
> (This was uncovered by a simple "make distcheck", which thankfully
> write-protects the source directory. I hope everybody uses "make
> distcheck" freely before checking in their changes, eh?)
>
> you can do more than hope: why not write down some good tips under
> workbook/build/ somewhere?
Ok, it's in HACKING.
> [cleaning not required in the presence of SCM_MAGIC_SNARFER]
>
> if you remove cleaning you need to promote SCM_MAGIC_SNARFER to required
> status and document accordingly.
It is already.
_______________________________________________
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 16:45 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 [this message]
2002-04-08 19:34 ` Thien-Thi Nguyen
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=873cy6f8av.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=bug-guile@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).