On Fri, Jul 30, 2010 at 10:50 AM, Chiheng Xu <[email protected]> wrote: > > Is 64-bits MSYS or Cygwin necessary? > > MSYS may be not necessary at all. > > If Cygwin merge the changes done in MSYS, and provide a Win32_Path > mode(translating all Unix paths to Win32 paths at fork/exec or spawn) > and MinGW transform itself to use binary mode(linking with binmode.o > instead of txtmode.o) and slightly patch uname.exe in coreutils, > Cygwin has the potential to replace MSYS and provide many tools > missing in MSYS, like tcl/tk, expect, dejagnu necessary for the > testing of GCC/GDB/BINUTILS. >
What I want to say is that, transform Cygwin to be universal POSIX command line environment for Windows. Cygwin's default mode is "Unix path mode", so it can't not launch native Win32 executable(like MinGW gcc) that require paths in their argv[] to be Win32 path. So Cygwin need to provide an optional "Win32 path mode", like MSYS do. But ordinary Win32 executable is linked with txtmode.o, which is not compatible with Cygwin's binary mode. So MinGW also need slightly transform itself to linked with binmode.o. Cygwin has an CYGWIN environment variable, can set the mode of cygwin1.dll . I believe Cygwin maintainer will accept to add an "Win32 path mode". -- Chiheng Xu Wuhan,China ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
