Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15779.16832.214809.113842@lemming.engeast.baynetworks.com>
Date: Tue, 8 Oct 2002 16:36:16 -0400
To: Robert Mecklenburg <mecklen AT cimsoft DOT com>
Cc: bug-make AT gnu DOT org, Cygwin Users List <cygwin AT cygwin DOT com>
Subject: Re: Changing resolution of $^ in make
In-Reply-To: <200210082030.g98KUMF26088@wolf.cimsoft.com>
References: <200210082030 DOT g98KUMF26088 AT wolf DOT cimsoft DOT com>
From: "Paul D. Smith" <psmith AT gnu DOT org>
Reply-To: "Paul D. Smith" <psmith AT gnu DOT org>
Organization: GNU's Not Unix!

%% Regarding Changing resolution of $^ in make; you wrote:

  rm> vpath %.in /c/work/tmp/src
  rm> vpath %.out /c/work/tmp/out

  rm> default: stuff/foo.out
  rm> 	# $^

  rm> %.out: %.in
  rm> 	touch /c/work/tmp/out/$@

  rm> the first time (when the prerequisite "stuff/foo.out" doesn't
  rm> exist) , $^ is resolved to "stuff/foo.out".  But the second time,
  rm> when stuff/foo.out already exists, it is resolved to
  rm> "/c/work/tmp/out/stuff/foo.out".  Is this behavior correct?

Yes.  VPATH/vpath is not appropriate for finding targets, only for
finding source files (that is, files which are not built by make but
which exist a priori).

See my web site below for a longer description of how VPATH/vpath
works.

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <psmith AT gnu DOT org>          Find some GNU make tips at:
 http://www.gnu.org                      http://make.paulandlesley.org
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/