Gnus development mailing list
 help / color / mirror / Atom feed
From: Denys Duchier <Denys.Duchier@ps.uni-sb.de>
Subject: Re: building pgnus with VPATH
Date: 13 Nov 1999 01:38:41 +0100	[thread overview]
Message-ID: <is7ljnb4z2.fsf@localhost.ps.uni-sb.de> (raw)
In-Reply-To: Jason R Mastaler's message of "12 Nov 1999 17:00:15 -0700"

Jason R Mastaler <jason@4b.org> writes:

> It would be nice if pgnus could be compiled in a separate directory
> than the sources, especially now that we can update via CVS.  
> 
> Although I'm not sure how to implement this

This request also gets my vote.  The autoconf documentation explains
the technique:

>   To support `VPATH', each `Makefile.in' should contain two lines that
> look like:
>
>     srcdir = @srcdir@
>     VPATH = @srcdir@

This is nice for several reasons: (1) you can have one source tree and
multiple build dirs for different architectures (or, in gnus case,
different emacs implementations) - this is great for updating in an
heterogenous environment, (2) you don't pollute the source tree, which
is great when you also participate in the development.  Less filling
_and_ tastes great!

Cheers,

-- 
Dr. Denys Duchier                       Denys.Duchier@ps.uni-sb.de
Forschungsbereich Programmiersysteme    (Programming Systems Lab)
Universitaet des Saarlandes, Geb. 45    http://www.ps.uni-sb.de/~duchier
Postfach 15 11 50                       Phone: +49 681 302 5618
66041 Saarbruecken, Germany             Fax:   +49 681 302 5615



  reply	other threads:[~1999-11-13  0:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-13  0:00 Jason R Mastaler
1999-11-13  0:38 ` Denys Duchier [this message]
1999-11-13  0:58   ` William M. Perry

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=is7ljnb4z2.fsf@localhost.ps.uni-sb.de \
    --to=denys.duchier@ps.uni-sb.de \
    /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 NNTP newsgroup(s).