Skip to content
Mikhail Titov edited this page Apr 27, 2015 · 6 revisions

Why CMake

With CMake one can easily

  • generate project files for all supported version of MS VC++
  • utilize all CPU cores with jom (a drop-in nmake replacement for parallel builds) to build everything faster

Why not to use official building system

There is nothing wrong with official build system and binaries when they are available. The problem arises when regular user tries to produce a custom build right here right now.

One has to use autotools to build gcc version first. On the way you'll get files for MS VC++ build. It takes twice time to build everything.

In most cases one already has CMake, python (3.2), and MinGW (with perl and patch) installed. So it makes sense to build MS VC++ version right away without intermediate steps.

How is it done

Once git repo is cloned/updated as well as gtk+ submodule, CMake pulls prerequisites for gtk+ from Fedora MinGW team repository using Maarten Bosmans' script. Then source code archives are downloaded from gnome server and NTFS hard links are created for corresponding CMakeLists.txt files inside of unpacked source code archives. Then some patches are applied.

What is missing

  • Debugging and patch submission to make gtkmm on Win32 even better.
  • As of now binaries depend on both msvcrt.dll and msvcr90d.dll (or alike). It worth a try to utilize ideas collected on xchat-wdk wiki page for binaries to depend solely on msvcrt.dll.

Similar projects