Actually building on multiple platforms without maintaining separate build files for each is the problem...
CMake was created to build Kitware's other products, most notably VTK and ITK. To date, I've built both, and other things built on top of them on three platforms, with several variations: GCC on Linux, both 32bit and 64bit, MinGW and Visual C on Windows. I don't need to install anything else apart from CMake and the compiler (and associated Make package) on each of those platforms, run it once, and the
In most cases, the MSVS project files are a courtesy for the people who are probably going to be using MSVS. I remember piles of 1990's open-source projects which ran on Windows, and everyone was asking for the project files. What is this other compiler you speak of - Cygwin isn't a compiler it's a fake unix environment, you can't make a Windows program without MSVS they say. Plus, whomever is doing the Windows port probably uses MSVS anyway.
For a true open-source solution, they would provide the command-line build. That way people can use the free version of msvs if they want. But for debugging and patching, and especially if I'm porting, I want to use MSVS because it's what I'm familiar with and it works.
Before.NET, I used to call MSVS the only decent software MS made, with SQL a close second. Not that they were perfect, but they were developed for coders by coders. Then it took 5 years for MSVS.Net to mature, and it's only getting better. But it's the standard, and the guy porting probably uses it, so why not include it.
The other compiler is MinGW32 [mingw.org] - there are others, like Borland C, and ICC...
I think CMake supports them all.
There are still piles of projects running on Windows. Right now, I'm on Windows (work machine), with KDE 4.4, Inkscape, Gimp, VTK and ITK among other things installed. Remember, lots of devs work on Windows, and quite a large body of users too. Not to mention other environments, like embedded systems which might or might not be able to work with full autotools...
The confusion of a staff member is measured by the length of his memos.
-- New York Times, Jan. 20, 1981
Autotools do not need a book (Score:5, Insightful)
... they should be replaced by something else.
Re: (Score:1, Troll)
Re: (Score:4, Funny)
Re: (Score:2)
Actually building on multiple platforms without maintaining separate build files for each is the problem...
CMake was created to build Kitware's other products, most notably VTK and ITK. To date, I've built both, and other things built on top of them on three platforms, with several variations: GCC on Linux, both 32bit and 64bit, MinGW and Visual C on Windows. I don't need to install anything else apart from CMake and the compiler (and associated Make package) on each of those platforms, run it once, and the
Re:Autotools do not need a book (Score:2)
In most cases, the MSVS project files are a courtesy for the people who are probably going to be using MSVS. I remember piles of 1990's open-source projects which ran on Windows, and everyone was asking for the project files. What is this other compiler you speak of - Cygwin isn't a compiler it's a fake unix environment, you can't make a Windows program without MSVS they say. Plus, whomever is doing the Windows port probably uses MSVS anyway.
For a true open-source solution, they would provide the command-line build. That way people can use the free version of msvs if they want. But for debugging and patching, and especially if I'm porting, I want to use MSVS because it's what I'm familiar with and it works.
Before .NET, I used to call MSVS the only decent software MS made, with SQL a close second. Not that they were perfect, but they were developed for coders by coders. Then it took 5 years for MSVS .Net to mature, and it's only getting better. But it's the standard, and the guy porting probably uses it, so why not include it.
Re: (Score:2)
The other compiler is MinGW32 [mingw.org] - there are others, like Borland C, and ICC...
I think CMake supports them all.
There are still piles of projects running on Windows. Right now, I'm on Windows (work machine), with KDE 4.4, Inkscape, Gimp, VTK and ITK among other things installed. Remember, lots of devs work on Windows, and quite a large body of users too. Not to mention other environments, like embedded systems which might or might not be able to work with full autotools...