Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Gradle vs Tup, 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 Gradle is ranked 11th. The most important reason people chose Tup is:
It is very fast.
Specs
Question Ranking
Pros
Pro Official Android Studio build tool
Android Studio's build system is an Android plugin for Gradle. What's more is that the Android Gradle plugin can be installed and run even on machines that don't have Android Studio, which enables you to build Android apps everywhere (for example continuous integration servers).
Pro Lots of plugins available
Gradle has hundreds of open source plugins available. This is extremely helpful for users who want to speed up their development.
Pro Dependency programming tool
Gradle is a dependency programming tool first and foremost. Gradle will make sure that all declared dependencies are properly executed for every random task that you execute in your setup. The code can be spread across many directories in any kind of file layout.
Pro Short scripts
Since Gradle does not use XML but it uses it's own DSL based on Groovy, Gradle scripts tend to be shorter than other build tools that use XML. Boilerplate code is also considerably small because it's DSL is designed to solve a specific problem: moving the software through its lifecycle starting from compilation into static analysis and testing, packaging and finally deployment.
Pro Integrates with Maven
Gradle can deploy to remote Maven repositories or even install to your local Maven repo.
Pro Built for continuous delivery
Gradle can be easily integrated with Jenkins to create a continuous delivery pipeline for any Java application.
Pro IDEA integration
Gradle has full integration with Jetbrains IDEA.
IDEA understands multi-module Gradle builds and automatically maintains the IDEA modules within the project.
You also have the option to run unit tests with either the built-in JUnit/TestNG test runner, or delegate running the test to Gradle using the same visualization as the built-in runner.
Pro Integration with Ant
Gradle integrates perfectly with Ant. Giving developers a lot of Ant's flexibility. You can run individual Ant tasks on Gradle or even entire Ant builds.
Pro Convention over configuration
Gradle follows the convention over configuration paradigm in order to make it easier for developers by having already made a number of decisions out of the box.
Pro Eclipse integration
Gradle has full integration with Eclipse through developer tools and plugins.
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.
Cons
Con Can get slow for large builds
Since Gradle uses Groovy instead of XML for it's configuration scripts, it achieves a great deal of flexibility but unfortunately that comes with slower builds when the project gets large enough. This is because the entire Groovy script has to be recompiled for every build instead of simply being parsed.
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).
