When comparing Tup vs Please, the Slant community recommends Tup for most people. In the question“What are the best open-source build systems for C/C++?” Tup is ranked 5th while Please is ranked 17th. The most important reason people chose Tup is:
It is very fast.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Speed
It is very fast.
Pro Tidy
It will automatically clean-up old files.
Pro General
Not bound to C/C++.
Pro Lua
Tup supports writing build definitions using Lua or Tupfiles.
Pro Cross platform
Supports Linux, OSX, and Windows.
Pro Cross-platform
Linux, macOS, FreeBSD.
Pro Intuitive syntax and workflow
Much simpler than multi-tier build systems, like Make and Ninja.
Pro Code Completion
Works with many IDEs, including Visual Studio Code.
Cons
Con Variants not working on Windows
The solution for having different build configuration (think Release/Debug) is broken on Windows.
Con Cannot incrementally modify or delete files
Cannot incrementally modify files (e.g. LaTeX PDF, VISing and LIGHTing Quake maps, which takes the same BSP file as input and output), and will not delete files (e.g. rm build/*.o).