Makefile_tutor
This project aims to create a crystal clear tutorial on a cryptic looking topic. (by clemedon)
shake
Shake build system (by ndmitchell)
| Makefile_tutor | shake | |
|---|---|---|
| 17 | 11 | |
| 588 | 757 | |
| - | - | |
| 5.6 | 6.2 | |
| 5 months ago | 11 days ago | |
| Makefile | Haskell | |
| Creative Commons Attribution Share Alike 4.0 | BSD 3-clause "New" or "Revised" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Makefile_tutor
Posts with mentions or reviews of Makefile_tutor.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-11.
-
What's the best way to convert my backend C++ code to a library?
Or directly with make and Makefile for such a simple task cf. version 4 -> https://github.com/clemedon/Makefile_tutor
- Makefile made simple + best practices once and for all [TEXT]
-
Need some help with Makefile
(this is a good example: https://github.com/clemedon/Makefile_tutor/blob/main/projects/v3/Makefile)
-
Recommended makefile resources
This was posted recently in this sub and it looks really well made: https://github.com/clemedon/Makefile_tutor
- Straightforward Makefile Tutorial that bring together best practices once and for all.
- Straightforward Makefile guide that bring together best practices once and for all.
-
GNU Makefile Tutorial (without headache) 🍃
→ https://github.com/clemedon/Makefile_tutor 👀
-
C's build system, a mystery for beginners
Take a look at this tutorial for Makefile.
- Makefile tutor
shake
Posts with mentions or reviews of shake.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-05.
-
Ninja is enough build system
Another interesting implementation is Shake: https://shakebuild.com/
It is technically a Haskell DSL, but supports Ninja files, time estimates and has tools for linting and profiling.
-
Buck2: Our open source build system
They explicitly refer to Shake build system and Build Systems a la Carte paper.
-
Straightforward Makefile Tutorial that bring together best practices once and for all.
The one paper that gave me hope about build systems was Build systems à la carte: Theory and practice, by Andrey Mokhov, Neil Mitchell, and Simon Peyton Jones. Among other things, it describes the theoretical underpinnings of the Shake build system. To be honest I believe any build system that ignores the maths described in this paper can safely be ignored. (You may however ignore the paper itself if the maths checks out. See Daniel J. Bernstein's redo, which matches Shake very closely.)
-
Worst language you ever used? Really used not just looked at the manual.
Yeah, they don't have to be terrible. I haven't used it, but people in my circles tend to really like Shake, which uses a Haskell embedded DSL to describe builds.
- Shake Build System
-
Strengths, weaknesses, opportunities, and threats facing the GNU Autotools
You could try Shake. It's a sane build system written by a former co-worker of mine. https://shakebuild.com/
-
Overview of the CMake controversy, and break down the pros and cons of the critical C++ tool.
Shake does require compilation as it's essentially just a Haskell library providing a DSL and it works just fine, I guess in gradle's case it's a thing about Java-typical overengineering and complete blindness to resource usage. Shake's underlying engine can actually go head-to-head with ninja itself when building ninja files.
-
Need recommendations for a dependency-tracking system
Did you look at shake: https://shakebuild.com/ ?
- The Shake Build System
-
Trouble Linking Dynamic Library for Package
For reasons I don't want to get into, I am building my own GHC package without cabal. The documentation is a little sketchy, but I've succeeded in build and installing it in my own user database (I'm on linux x86_64, using GHC 8.6.5). I am using shake to do all of this, and I've been pretty pleased with how it works.
What are some alternatives?
When comparing Makefile_tutor and shake you can also consider the following projects:
nobuild - Header only library for writing build recipes in C.
gitHUD - command-line HUD for your git repo
42_CheatSheet - A comprehensive guide to 50 years of evolution of strict C programming, a tribute to Dennis Ritchie's language
marvin - The paranoid bot (framework)
FPGA-blinky
leksah - Haskell IDE
Multipipe_tutor - C multi-pipe implementation, dissection and explanation.
shake-language-c - Cross-compilation framework based on the Shake Haskell library.
Crystal-Web-Framework
bumper - Haskell tool to automatically bump package versions transitively.
generic-template - A generic template for GitHub repos. While it is primarily intended for Python project, it can be used as a reference for projects in other languages as well.
clone-all - clone all the github repositories of a particular user.
Makefile_tutor vs nobuild
shake vs gitHUD
Makefile_tutor vs 42_CheatSheet
shake vs marvin
Makefile_tutor vs FPGA-blinky
shake vs leksah
Makefile_tutor vs Multipipe_tutor
shake vs shake-language-c
Makefile_tutor vs Crystal-Web-Framework
shake vs bumper
Makefile_tutor vs generic-template
shake vs clone-all