This is the mail archive of the
cygwin-developers@sources.redhat.com
mailing list for the Cygwin project.
Re: moving testsuite 1 level up
- To: Chris Faylor <cygwin-developers at sources dot redhat dot com>
- Subject: Re: moving testsuite 1 level up
- From: Egor Duda <deo at logos-m dot ru>
- Date: Fri, 1 Sep 2000 11:29:59 +0400
- Organization: DEO
- References: <130300190981.20000901001144@logos-m.ru><200008312018.QAA25051@envy.delorie.com><173301615790.20000901003528@logos-m.ru> <20000831165739.A15144@cygnus.com>
- Reply-To: Egor Duda <deo at logos-m dot ru>
Hi!
Friday, 01 September, 2000 Chris Faylor cgf@cygnus.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@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19