The venerable UNG Make: An ancient build tool that works great and is still better than most alternatives
Use Cases and Deployment Scope
Our team uses GNU Make to build any of our software projects once they have reached a reasonable level of complexity. We use it to build Go, C, and Fortran-based projects to provide simple "make build" or "make test" steps to compile code and run tests. It's an old-fashioned tool, and I wish there were better tools available, but none of the contenders seem to have the simplicity and extensibility that Make does. Other devices seem to be language-specific and specialized for specific ecosystems (e.g., maven or Gradle are great for Java, but not for C projects). Batch files are simpler but don't perform as well and don't provide as much out-of-the-box flexibility (e.g., ability to compile only specific files rather than a full build).
Pros
- Dependency tracking (only re-build files if needed)
- Simple to integrate with existing command-line tools
Cons
- No dependency management tools (but there are no cross-platform tools of this type anyway)
- Tedious to do cross-compilation (Debug & Release builds, 32- and 64-bit builds, x86/ARM builds)
Likelihood to Recommend
GNU Make is a great tool for simple builds where language-specific options are not available, or to provide shortcuts for common commands (e.g., "make build" as shorthand for "go build ..." with a bunch of flags). However, it is complementary to other build systems. It does not replace them, which is perhaps one of its greatest strengths as well (works with existing ecosystem instead of trying to do everything). GMU Make it simple to get started with, and the philosophy of understanding how sources map to outputs, as well as the dependency graph, are beneficial.
