2013/6/11 Corinna Vinschen <vinsc...@redhat.com>: > On Jun 11 16:59, LRN wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 11.06.2013 16:14, Corinna Vinschen wrote: >> > On Jun 11 12:58, Ray Donnelly wrote: >> >> I for one am hugely appreciative of all the hard work that Corinna, Kai, >> >> redhat, the mingw-w64 team and also Alexey has put into both Cygwin and >> >> MSYS2. >> >> >> >> Cygwin and MSYS2 exist for different, mutually exclusive goals. Anything >> >> we >> > >> > I fail to see that. MSYS2 is basically to run a Mingw compiler and to >> > have a POSIX-like shell. How is that something Cygwin doesn't provide >> > anyway?!? >> Cygwin doesn't seem to have the mangling (that is, converting paths like >> /usr/local/include/glib to C:/foobar/baz/usr/local/include/glib). > > Cygwin has the cygwin_path_conv call which allows to convert paths > from POSIX to Windows and vice versa, including long paths > 260 chars. > > You can also use Windows path as input. `find C:/' works. > >> I'm sure that Alexey will be able to give you a complete list of things >> that Cygwin can't do, but MSYS2 can (or should be able to) do. > > Just as a sidenote, a ChangeLog.MSYS or something like that in the > sources would be helpful. > > > Corinna
Hmm, isn't the maintaining of ChangeLog not mandatory for GPL? Anyway, I have one question about term msys-toolchain. What actual is here the difference to cygwin, if there is any? [I don't speak about the native-Windows Toolchain end-user in general are using]. As msys isn't a known target upstream on gcc/binutils/etc, I would strictly recomment to use here instead cygwin-triplet anyway. Kai ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
