Christian Ehrlicher wrote:I still don't understand why msys is needed anyway. Because it exists and people use it. It is a standard support drill for various people. That said, I'm not pleased with the official MSYS distribution as of late. It runs ./configure stuff rather badly, and I need that for legacy build support. Also for the plethora of 3rd party libraries that only have a ./configure, that I'm not going to CMakeify. We're compiling kdelibs / kdepimplibs & kdebase with cmake on a native cmd.exe environment with msvc and mingw and never had a need to use the msys shell. I personally avoid this msys and write a small cmake script to get around the use of ./configure. We're not interested in rewriting all the build systems for all the 3rd party libraries that people typically need for MinGW development. Even if we were, they wouldn't get used and tested. The reality is that lotsa stuff is going to be using ./configure for awhile. Also it's an aide de port. It is much easier to port Unixy things to Cygwin, and then to MSYS, before worrying about making them "clean" for the Windows Command prompt. Cheers, Brandon Van Every |
_______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
