When I tried, your sample seems to work with make->clearmake when
SHELL=CMD.EXE but not on sh.exe of Cygwin B20.1. We use Gnu Make 3.78.1
which is the first to work ok on the B20 shell. But we really don't want to
go back to CMD.EXE when we aim for clearmake compatibility :-(
Sten Rosendahl, IMI Corp.
-----Original Message-----
From: Guy T. Moore Jr. [mailto:gmoore@openmarket.com
I am on WinNT 4.0 using ClearCase 3.2.1-20, and using Cygwin v1.0 as my
SHELL.
I can't seem to execute Cygwin's make and have it call clearmake which
then calls clearmake one more time.
If I keep the test to only using make, then it works.
If I keep the test to only using clearmake, then it works.
If I call clearmake first, then use make inside the makefile, then it works.
I just can't call make first then be using clearmake inside the makefile.
Anybody run into this problem? and then have a solution...
<--cut-->
Reason why I need this capability.
Some targets build programs that ask for input from user.
clearmake does not support interactive programs, thus must use make
from start to finish. Other targets I want to use clearmake.
So there is a decision process embedded in the makefiles whether to
switch to different makes and would like to keep them there.
(Aside: clearmake does NOT work with Cygwin B20.
clearmake DOES work with Cygwin v1.0 withoug modifications to
sh.exe
although I have other issues with Cygwin v1.0 whereas v1.0 does not
behave
like b20. Some for the better, some for the worse.)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:23:30 EDT