On 5/26/06, Andy Dougherty <[EMAIL PROTECTED]> wrote:
I don't know anything about either msys or mingw, so I don't really know
what to recommend.
I'm afraid I don't understand what a patch would actually try to do.
From your previous message, it looks like sh.exe is changing the path
delimiters and shell escapes so that things don't work anymore. Are you
trying to patch Configure.pl to handle those changed delimiters and shell
esacapes? Or do you have something else in mind?
The patch would be nothing more than a warning. As I said, the PATH
environment has absolutely no effect on the configure process, just the
build process. During the configure process, we can warn the user that the
build process won't work unless they do something about their PATH. In
particular, prevent mingw from using msys and subsequently changing the the
behavior of path delimiters and shell escapes.
I would love to submit a patch to make using msys transparent and "just
work" but after searching the archives, it appears that people working on it
far longer than I have had little to no luck with it and I am just getting
my feet wet again.
Also, what's the preliminary setting of $make got to do with it? You've
still got to call some sort of make command in the end.
It may seem odd to some to put a warning for $make as mingw32-make in a
section of code when $make is actually nmake at that point. Placing it at
the end of Configure.pl may make more sense since it is the last set of
instructions to the user but it appears that a lot of work has gone in to
making it platform neutral.
If you're just wondering where '$make' gets set, then config/inter/make.pm
is where to look -- it seems to prefer mingw32-make over nmake. Perhaps
that's wrong.
I don't think it is wrong but perhaps the order of hints/make should
change. I don't know that's why I am asking.
--
Andy Dougherty [EMAIL PROTECTED]
Cheers,
Joshua Gatcomb
a.k.a. Limbic~Region
