FINDING 01·Windows developers (Fortran/C projects)·1 source
Make's poor cross-platform behavior on Windows
Users on Windows encounter friction with GNU Make due to path separator mismatches (slash vs. backslash) and shell-determination issues, making it unreliable for Windows-based development workflows.
Source
“I've read a little about gnu make, and that its got some issues on windows platforms (from slash/backslash, to shell determination ...)”
FINDING 02·Java/XML developers migrating from Ant to Make·1 source
Difficulty migrating Ant-specific tasks (e.g. XSLT) to Make
Developers converting Ant build scripts to Makefiles hit a wall when trying to replicate Ant-specific tasks like XSLT transformations, for which Make has no native equivalent, requiring significant manual effort.
Source
“I am going to convert an Ant script to a Make file. I have finished lot of conversion part of it. But that ant script has small code like below, <xslt in="" out="" style="../profiling/profile.xsl"> ... How should I write above "xslt", "in", "out", "style", and "param name" parts of ant script in my Make file? I tried and searched about that conversion so many times, but I couldn't find it.”
FINDING 03·Build-tool evaluators and open-source tool authors·2 sources
Alternatives to Make lack adoption despite measurable improvements
Even when alternatives offer clear technical advantages, they struggle to gain traction — leaving users uncertain whether to invest in them, and builders of alternatives unsure how to compete with Make's entrenched position.
Source
“Are there measurable benefits to the alternatives, or are the 'market shares' due mostly to opinion and experience of team leaders?”
Source
“What forces are at work keeping crufty old Make (with or without makefile generator tools) prominent as a build tool? Is it deficiencies in alternatives that keep them from being widely adopted, or insufficient publicity, or does something about Make keep it in place?”
FINDING 04·General software developers and build-system maintainers·2 sources
Make's implementation quality and complexity despite sound core concept
Long-time Make users acknowledge the underlying concept is valid but find the actual implementation lacking, prompting a sustained search for alternatives that don't over-engineer the problem. This is a recurring sentiment spanning from 2008 through 2022.
Source
“I've been using make and makefiles for many many years, and although the concept is sound, the implementation has something to be desired.”
Source
“Are there any new Make alternatives that I should try for building a multi-language, monorepo project that also has a number of Linux system dependencies?”
FINDING 05·Teams managing large codebases or monorepos·2 sources
Make struggles to scale to large or multi-language projects
Despite Make's dominance, users and observers note it has well-documented weaknesses when dealing with large projects, yet alternatives have failed to displace it — leaving teams stuck with a tool that doesn't serve complex, multi-language or monorepo setups well.
Source
“Despite Make's many weaknesses and difficulties dealing with large projects (e.g. see http://freshmeat.net/articles/what-is-wrong-with-make) it appears to still be more widely used than newer, improved alternatives such as Scons, Jam, Rake, Cook, and others.”
Source
“Are there any new Make alternatives that I should try for building a multi-language, monorepo project that also has a number of Linux system dependencies? For some context the languages will definitely be Python and Julia, with possibly Rust, C/C++, and CUDA.”