Since CMake 3.16, there's the target_precompile_headers command that lets you add a list of header files to precompile. But the days of searching the web for snippets to enable precompiled headers in CMake are over. If the toolchain supports it, one can speed up compilation by precompiling header files.įor the longest time, CMake did not offer out-of-the-box support for that. That is especially true for library headers. In a C++ project, the same header files are potentially included over and over again. Let's have a look of the CMake improvements that Qt's build tool switch caused or influenced. Qt supports different ways of building it (prefix, non-prefix, different feature sets) Qt is split into modules that can be built stand-alone or all-in-on. That's why we collaborated with Kitware to get the obstacles out of the way and improve CMake for the benefit of the Qt Project and the larger CMake community.īuilding Qt is complex, due to various contributing points: Now the essential migration work has been completed and it's time to share our findings.Īlthough well established and used by many projects, CMake was missing some key features that were supported in the previous Qt build tools. In addition, migrating to CMake gave us an opportunity to get rid of the maintenance burden of our internal build tools.Įven bigger than the decision was the effort required to migrate to CMake. According to the studies at that time, CMake was clearly the most commonly used build tool among Qt users - qmake aside. Most Qt users wanted to have easier integration of their Qt projects with the rest of their software. The main reason for the decision was user feedback. We made a big decision to start using CMake to build Qt 6 one and a half years ago. Wednesday Januby Jörg Bornemann | Comments
Qt and CMake: The Past, the Present and the Future
0 kommentar(er)
