Overview of the CMake controversy, and break down the pros and cons of the critical C++ tool.

• shake

  11 757 6.2 Haskell

  Shake build system

Shake does require compilation as it's essentially just a Haskell library providing a DSL and it works just fine, I guess in gradle's case it's a thing about Java-typical overengineering and complete blindness to resource usage. Shake's underlying engine can actually go head-to-head with ninja itself when building ninja files.

• cppreference-doc

  56 405 0.0 HTML

  C++ standard library reference (by p12tic)

https://en.cppreference.com/ is an absolute godsend and most things there have very explicit documentation and usage examples.

• 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.

  

• tup

  23 1,144 7.7 C

  Tup is a file-based build system.

The problem is that asciidoctor doesn't have a -MMD option like gcc. So you have to list out all dependencies explicitly. The only ways to fix this are to look at what files asciidoctor opens and calculate dependencies based on that, send a patch to add this kind of option, or create your own asciidoc parser just to extract dependency info. Note, however, that this is not a make problem. Every build tool runs into this issue.

• zig

  818 30,946 10.0 Zig

  General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.

  

For context: https://ziglang.org/

Suggest a related project