Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Fri, 1 Sep 2000 11:29:59 +0400
From: Egor Duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.45) Personal
Reply-To: Egor Duda <deo AT logos-m DOT ru>
Organization: DEO
X-Priority: 3 (Normal)
Message-ID: <2340886468.20000901112959@logos-m.ru>
To: Chris Faylor <cygwin-developers AT sources DOT redhat DOT com>
Subject: Re: moving testsuite 1 level up
In-reply-To: <20000831165739.A15144@cygnus.com>
References: <130300190981 DOT 20000901001144 AT logos-m DOT ru>
 <200008312018 DOT QAA25051 AT envy DOT delorie DOT com>
 <173301615790 DOT 20000901003528 AT logos-m DOT ru> <20000831165739 DOT A15144 AT cygnus DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

Friday, 01 September, 2000 Chris Faylor cgf AT cygnus DOT com wrote:

>>DD> Perhaps it's time to update Maekfile.common to use some $(UPTOP)
>>DD> (defined to ".." in most cases) variable?
>>
>>i  wanted  to  to  that but stumbled over code in Makefile.common that
>>sets updir* and bupdir* vars. i don't understand why not just set them
>>.. , ../.. and ../../..

CF> They are set to that in some cases.

i've   never seen the case when pwd don't return an absolute path. but
i agree that relying on it isn't good.

>>and  don't  feel  i  can  mess with the code i don't fully understand.
>>maybe someone enlighten me on this subject?

CF> It's because I don't like to see ../../../../libbfd.a on a command line.
CF> I'd rather see /foo/bar/bfd/libbfd.a and we can rely on the fact that
CF> gnumake is available for filename parsing.

i see. as for $(UPTOP), maybe instead of

bupdir1:=${patsubst %:::,%,${patsubst %/:::,%,$(dir $(bupdir)):::}}

we should define

broot:=${shell cd $(UPTOP)/..; pwd}
btargetroot:=${shell cd $(UPTOP); pwd}
srcroot:=${shell cd $(srcdir)/$(UPTOP); pwd}

and then (in the individual Makefile.in's) we'll use not paths with
$(bupdir2),  $(bupdir1)  but  paths  relative  to  $(btargetroot)  and
$(srcroot )or (in few occasions) to $(broot)

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19