MSYS mode (continue)

Corinna Vinschen corinna-cygwin@cygwin.com
Tue Jul 30 09:04:00 GMT 2013


On Jul 30 04:45, LRN wrote:
> On 29.07.2013 19:47, Corinna Vinschen wrote:
> > On Jul 29 19:36, LRN wrote:
> >> I would expect people to get cygwin/msys in one place, and get MinGW in
> >> another. Even mingw-get, while being a source of both msys and mingw
> >> packages, clearly distinguishes betweent he two.
> > 
> > That's what I understood differently.  From the discussion on mingw-w64
> > it seemed that a mingw dev using Cygwin/MSYS would prefer if the default
> > gcc creates non-CYgwin/MSYS, but rather Windows-only binaries.
> 
> The problem is not that you can't have a W32-targetted gcc.exe in /usr/bin.
> 
> The problem is that the convention that everyone has been following for
> years now is that all mingw stuff lives in /mingw, and all msys (cygwin)
> stuff lives in /usr. These two are never mixed.
> [...]
> So i'd suggest to stick with /usr and /mingw convention and let mingw
> take care of itself. It's simpler that way.

Fine with me, of course.  I don't have that problem myself so whatever
works better for you is ok.  But then the number of changed packages
doesn't really matter.  From my POV MSYS sticks to being it's own distro
with another focus than the Cygwin distro.

So we're back to discussing in how far MSYS can be implemented using a
stock Cygwin DLL under the hood and the tweaks being in an external MSYS
DLL so users can mix the best of both worlds as they see fit for their
purpose.

Are you going to help implementing this?  If not, I'm missing input
from any of the developers working on MSYS2...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat



More information about the Cygwin-developers mailing list