Mail Archives: djgpp/1998/10/23/11:42:00
Hans-Bernhard Broeker wrote:
>
> Of course it will. How on earth do you expect DOS's 'cd' command to
> understand *forward* slashes?
The djgpp port of 'make' is intelligent enough to feed the corrected
slashes
to command.com if a unix-like shell can't be found. The only thing it
doesn't
do is invoke another shell and make when recursing with command.com.
> OTOH, 'make' behaviour isn't all to portable, anyway, so my recommendation
> would be: required GNU make to be used, and use its
>
> $(MAKE) -C ../original
I haven't tried this solution yet, but I will. What I am doing is a port
of Midnight Commander.
I have been trying to do minimal modifications to the MC distribution,
and still have a source
distribution that can be built on a DOS platform, with only utils ar,
rm, and cp installed, and
still build on a LFN system with bash and all its friends.
Like many projects, some of these goals conflict with each other, but I
am very close to resolution.
The source will never auto-configure and configure on straight DOS, but
at least I want the makefiles
to work with no editing.
> The main difference is that the 'current working directory' has a
> *totally* different meaning on DOS and Unix:
how true. I am not targeting Unix at all, just the djgpp community from
the straight DOS setup
with just gcc and binutils on a 8.3 platform, to someone with all the
unix shells and utilities on a LFN system.
- Raw text -