From: Peter S. <pe...@st...> - 2010-12-06 23:44:46
|
Xiaofan Chen wrote: > I think you guys have some mis-understandings about MSys > and autotools. I'll try to clarify what I meant. > MSys autoconf is to created MSys dependent applications and this > is not what we want, we want to create Windows native binary. I think MinGW is only GCC and toolchain. And MSYS is the environment that allows to run pre-generated configure scripts, to generate Makefiles that will then use MinGW to build native Windows binaries. autoconf would be compiled by MinGW (probably) and run in MSYS. That's why I called it MSYS autoconf. > Secondly MSys still use shell scripts similar to Unix and > Cygwin, you can call it a mini shell environment but nevertheless, > it is similar to Unix and Cygwin when it comes to shell scripts. Yes! This is the primary task of MSYS as I understand it. And it is even the exact same bash as many Unix systems and Cygwin. But not every command line tool is available, so I agree that it can be called minimal. It's also what the M stands for. :) (But I actually think that the default MSYS installation is very competent!) > If you ever use MinGW/MSys, and open the include > files or the shell scripts (many under the bin dir > are shell scripts), you will notice they are not > CRLF. Ok! The include files in my MinGW cross-compiler toolchain are also LF only, but exactly because it is a cross-toolchain I didn't bring it up, since it may have been adjusted to my platform. > If you think CRLF is native and MinGW/MSys > is Windows native and thus should use CRLF > for everything, then you are totally wrong. Thanks for adding this piece of the puzzle! //Peter |