In long-running projects maintaining the sanity of visual studio projects and solutions is a pain, to put it mildly. The CMake storm was twenty years in the making! Now that it has reached the plateau of productivity and the hype cycle has ended, let us see some of the success stories and why you should take modern CMake seriously. From Visual Studio 2017 to Qt 6.0 now deciding to support CMake, I believe, CMake currently has reached its plateau of productivity. Modern CMake (Versions after CMake 3.0) dropped many anti-patterns of classic CMake and has been riding on the Slope of Enlightenment. It then took a painstaking wait of around ten years to release CMake 3.0 during which CMake – I would claim – went through the trough of disillusionment. This came as a major triumph for CMake and – as it seems – to be the peak of Inflated expectations. In 2006, KDE successfully migrated to CMake leaving behind their aging autotools build system. Within the next five years, CMake was well recognized as a viable solution to build large open-source and proprietary projects alike. The initial version was released by Kitware in the year 2000. Image source: Gartner (I’ve added the years to the original image) Without much ado, let us start with the standard Gartner hype cycle framework and overlay the stages CMake went through in it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |