Von: "Kai Sterker" <[EMAIL PROTECTED]> > On 9/26/06, Brandon J. Van Every <[EMAIL PROTECTED]> wrote: > <snip> > > In the meantime, you might consider using > > CMake "in the standard way" to get around your problems. > > Well, I can specify all those libs and headers cmake couldn't figure > out manually, but I had hoped for it to work without user > intervention, just like on a proper UNIX. I know that only developers > will probably ever want to compile my application on Windows > themselves, so it shouldn't matter if the process is a bit rough. But > I thought that this would be an opportunity for improving an otherwise > great tool, so I wanted to let you know. (Being selfish here, I know > ;-)) I still don't understand why msys is needed anyway. 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.
Christian -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
