On 12/1/2012 06:49, Pau Garcia i Quiles wrote: >> Now of course, we could >> try to provide these system-specific files that cmake should be giving >> us for free, but then we'd have to maintain (thus somehow be able to >> test) every conceivable system that our users might have or want to >> use. >> >> > No, you don't. Either you have not used CMake enough or you have not > understood how it works. It's either CMake's or the user's mission to take > care of "every coneivable system", not the developer's (at least, no more > than in autotools). > >
I tried cmake, it didn't like that I was trying to use MSVC inside Cygwin by making too many assumptions in the generated makefile. The produced Makefile was not gmake compatible. I thought cmake was supposed to be better than autotools in the recent discussion. > > When I want to compile an autotools project, I need sh, which as you have > already said, is only half-legged available on Windows. And that's the > whole point of CMake, especially when Visual C++ is in the middle. Sure, > you can generate makefiles which call cl.exe, link.exe, etc, but in the > end, debuggin, profiling, distributed compilation will be a pain, whereas > they will work perfectly fine in projects using CMake. > As mentioned above, I redid my project with autoconf, automake and libtool.It drove MSVC drivers in Cygwin just fine, whereas cmake refused to do so. > Requiring CMake, a self-contained tool with no dependendies, to compile a > project using a CMake buildsystem is no big deal. It might have been 5 > years ago, it is not now. Even less on Windows. > Instead of a shell, you just moved it to an opaque Makefile generator. > Oh, and there is one more nicety about CMake: there is a GUI for users to > configure optional dependencies, this-or-that option, etc. > configure --help. > But I'm tired of this discussion. I'll keep using CMake until I find > something better. So far, I have not. Neither for open source, nor for work. Still not seeing the advantage of cmake, other than it's new and shiny.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: INSIGHTS What's next for parallel hardware, programming and related areas? Interviews and blogs by thought leaders keep you ahead of the curve. http://goparallel.sourceforge.net
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
