Re: Building Emacs from a new MinGW environment

[Eli Zaretskii]

> Date: Mon, 16 Sep 2013 21:25:29 +0200
> From: Dani Moncayo <address@hidden>
> Cc: Emacs development discussions <address@hidden>
> 
> >> Mmm, but I don't see what wrong with a path like
> >> "/home/dani/whatever".  It is a perfectly legitimate MSYS path (like
> >> "/c/msys/home/dani/whatever" or "c:/msys/home/dani/whatever"), isn't
> >> it?
> >
> > It is, as long as it is used by MSYS programs.  But it is not
> > legitimate when it is passed to MinGW Emacs, because Emacs will not
> > find this directory.  Which is exactly what happens in your case.
> 
> I see.  But then, why doesn't the configure/build process make the
> translation when needed?

Because I don't know how to do that.  Is there any MSYS command that
would add the missing leading directories?  Patches welcome.

> If that "automatic translation" is difficult to implement, then I
> think that Emacs at least should document the limitation

Will do, if no other solution presents itself.

> and also add some check to the configure script in order
> to catch this use-case and stop the process with a helpful message.

If we can identify this use case, we are more than half-way towards
solving it.  IOW, I don't know how to identify it.