On Fri, 26 May 2006, Joshua Gatcomb wrote:
> 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.
Ok, if that's all you want to do, then I think checking PATH in the mingw
hints file and aborting with a message instructing the user to change PATH
is probably the right thing to do. (Yes, I know that changing PATH as
recommended won't affect the Configure process, but the user has got to
fix it before the build process anyway, and putting all that info in
the hints file makes it more likely that the right people will read,
understand, and maintain it in the future.)
> 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.
Fair enough. I had misunderstood and thought that, perhaps, simply using
'nmake' instead of 'mingw32-make' might have make it "just work". Oh
well.
--
Andy Dougherty [EMAIL PROTECTED]
