Top 11 Shell Makefile Projects
-
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
-
-
-
-
-
yplatform
Self-service bootstrap/build/CI/CD. Software and configuration that supports various cycles of software development.
-
Nutrient
Nutrient - The #1 PDF SDK Library. Bad PDFs = bad UX. Slow load times, broken annotations, clunky UX frustrates users. Nutrient’s PDF SDKs gives seamless document experiences, fast rendering, annotations, real-time collaboration, 100+ features. Used by 10K+ devs, serving ~half a billion users worldwide. Explore the SDK for free.
-
-
Makefiles are an eerily lisplike turing tarpit. I hand wrote the makefiles for my projects, they generate wonderfully organized build trees. Hell I use makefiles to manage my dotfiles repository, even blogged about it.
https://www.matheusmoreira.com/articles/managing-dotfiles-wi...
The sanest way I've found to write makefiles is to think of it as a tool that maps input paths to output paths. When compiling a program, I want to map source/program.c to build/$(config)/program. So I write pattern rules that do just that. Then I write make functions to convert paths in some tree to paths in another tree, which makes it easy to declare dependencies which then match the pattern rules. These functions are then helped by lots and lots of project specific variables to organize things.
Using make without phony targets is insane. Without phony targets, I'd need to type things like "make build/aarch64/executable" in order to get a build started. So I use phony targets for everything.
It got to the point I created a phony-targets shell script which parses make's database output and processes it into a sort of help text for any given makefile's phony targets interface:
https://github.com/matheusmoreira/.files/blob/master/~/.loca...
-
-