Good reasons to NOT use CMake

• nsbuild

  1 0 7.9 C++

• cppfront

  4 68 4.9 CMake

  CMake wrapper around the cppfront repository (by modern-cmake)

  

For another example, the CMake wrapper I wrote for cppfront automatically translates .cpp2 files to .cpp. This is simply impossible in Meson which, again, requires end-users to find the cppfront binary, write a generator rule, and then run it.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• cmake-init-use-pkg-config

  2 4 2.6 CMake

  Using a dependency that does not support clients using CMake

You have to realize that the point of using CMake is not entirely about your project, but about downstream users who wish to use CMake as well. If you do not support clients using CMake (i.e. install a CMake package) you are forcing every downstream user to figure your requirements out by themselves, which even for a project with no dependencies is non-trivial: https://github.com/friendlyanon/cmake-init-use-pkg-config

• meson-brainfuck

  4 10 0.0 Meson

  A proof that Meson is actually Turing-Complete

Meson is not capable enough. It lacks ways to create abstractions. It also advertises itself as not being turing complete, which is not only unimportant, but also false.

• ProxImaL

  1 111 7.0 Python

  A domain-specific language for image optimization.

  

• meson

  111 5,278 9.8 Python

  The Meson Build System

  

Suggest a related project