Mail Archives: djgpp/2001/12/26/10:34:06
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote in message news:<3C25BBD6 DOT 69061DAF AT is DOT elta DOT co DOT il>...
> > From: big10p AT hotmail DOT com (Chris Chadwick)
> > Newsgroups: comp.os.msdos.djgpp
> > Date: 20 Dec 2001 09:08:48 -0800
> >
> > The main reason I was thinking I'd have to use an alternative shell to
> > command.com, was because of this example from the make docs:
> >
> > %.d: %.c
> > $(SHELL) -ec '$(CC) -M $(CPPFLAGS) $< \
> > | sed '\''s/\($*\)\.o[ :]*/\1.o $@ : /g'\'' > $@; \
> > [ -s $@ ] || rm -f $@'
>
> You can eat that cake and have it, too: add "SHELL = /bin/sh" line to
> your Makefile, and Make will invoke Bash to run commands such as the
> one above. You don't need to make Bash your interactive shell for
> this to work. (You _do_ need to install the ported Bash, though.)
This was what I was getting at in my OP although I probably didn't
word it very well. I'm still a bit confused about "SHELL = /bin/sh"
though: doesn't this make sh.exe the default shell, not bash.exe? Or
is sh a part of bash? Sorry, but like I said, I'm not familiar with
all this posix/unix stuff, yet :)
- Raw text -