Message-ID: <3630ABEB.CF7CC06F@montana.com>
Date: Fri, 23 Oct 1998 10:16:43 -0600
From: bowman <bowman AT montana DOT com>
X-Mailer: Mozilla 4.5b2 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: Recursive make: portable technique?
References: <362FF086 DOT BDA6266C AT montana DOT com> <70pq3u$cju$1 AT star DOT cs DOT vu DOT nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com



Boon van der RJ wrote:
> 
> So bottom line is: I don't think there will be a problem with such an
> approach (not even taking into acount the unlikeliness of the tree set
> up and use of it described above)

I did some more testing, and found that the makefiles i'm working on did
indeed break. 
unfortunately, I have the line:

cd ../slang/src; $(MAKE)

to get DOS command.com to work, I need to 

cd ../../src  to get back to the original directory. If bash has already
returned, this line fails. 
I guess I can do it with a ../slang/makefile that then calls
src/makefile and back out of
the nested directories one by one. 

Or, just have a makefile.dos that will work with command.com. I've
already had to do a number of hacks. For instance, the original package
has a make.common include file that gets sliced down by pkunzip on a 8.3
system to the unfortunately named 'make.com'.