And here is the #nix way
#Makefile
I did not see anybody do this, so I am sharing it.
There is semi-nice way to get a per-rule software environment in #makefile .
Here is an example with #guix :
(i didnt manage to format the code on mastodon ..., code is in alternative text)
[Veille 📣] Non, les Taskfile ne sont pas plus simples que Makefile | Metal3d
https://www.metal3d.org/blog/2025/makefile-est-bien-plus-simple-que-taskfile/
Moi j’suis nul en Makefile, mais moi j’adore les Makefiles, alors merci @metal3d de remettre les points sur les i.
Makefile c’est trop bien, punkt schluss. Arrêtez de vouloir réinventer la roue avec des trucs plus récents si ça n’apporte rien pour le 99% des cas d’usages. Merci.
edit: Avant que ça chouigne dans les chaumières, ce que je demande à un outil comme Makefile c’est de permettre aux personnes qui sont nulles à l’utiliser (comme moi) d’en faire un usage qui correspond exactement à ce dont elles ont besoin. Et c’est le cas. 👍
Toute ma veille est disponible ici : https://links.vulgarisons.info/
#makefile #make #taskfile #programmation #automatisation
#links #veille
The biggest gripe in #embedded #development is the crappy IDE's from vendors. I much prefer to build from barebones #makefile projects.. you're free to use any text editor you wish.
https://github.com/cpq/bare-metal-programming-guide gets you started, especially if you're coming from #arduino style development!
As an inspiration, here's my repos for simple #MCU's from two mainstream vendors.
stm32G0: https://code.simplycreate.online/ajit/stm32g0cube-projects
mspm0g: https://code.simplycreate.online/ajit/mspm0
Saving valuable tokens with Makefiles
https://edleeman.co.uk/notes/saving-tokens-with-quiet-makefiles/
I remember someone mentioned using PHP as their static site generator and I was intrigued because PHP is an old and established way of doing "page templates" that it would be Cool to re-use instead of downloading a bespoke site generator tool
the problem is of course that php doesn't have any sort of "make static" command. but what it DOES have is a built-in server so that you can test out your php files.
so.
I wrote a makefile that serves a php file over localhost and then downloads from localhost to static html.
might polish this later but here's my work if you want to copy it:
https://github.com/nycki93/xp-php-wget
edit: i knew i'd seen this somewhere! @alterae does this on its site, but with a different makefile strategy: https://git.sr.ht/~alterae/alterae.online/tree/main/item/Makefile
#programming #website #php #makefile
My #artisinal, no-preservatives-added, all-organic #makefile for my #gamedev #project is over 850 lines long. So #anti #generative that not even cmake is allowed. #programming #cpp #c #homebrew
Anyone here managing their experiments/workflows with gnu #make ? Any tips ?
I was a #snakemake user, but I switched to #makefile recently because of the increasing complexity/bloat of Snakemake and I don't need the majority of the features... (plus colleagues were not using/familiar with Snakemake)
The make language is for sure less user-friendly than Snakemake's, but I'm still able to do what I need/want (just with more boilerplate).
I had to write small Makefile functions to keep some of my sanity...
(BTW: `.RECIPEPREFIX` let you redefine the prefix instead of the annoying tab! [1])
From what I understood, GNU Make can be extended with #guile [2], maybe that could help ? (but adds another dependency tho...)
TL;DR: I just want a simple/easy/lightweight/expressive workflow manager... 😔
[1] https://www.gnu.org/software/make/manual/html_node/Special-Variables.html
[2] https://www.gnu.org/software/make/manual/html_node/Guile-Integration.html
https://fundor333.com/post/2026/why-do-i-disinstall-poetry-and-use-only-uv-/
#poetry #pipenv #pyproject #pyenv #uv #makefile #make #precommit #dev #fingerfood
Made the switch from #ActualBudget to #beancount for my personal finances
The ecosystem is nice
- #fava, #beangulp for imports, #beanahead for recurring transactions, #favaCustomDashboards for charts, and #favaInvestor for portfolio tracking
Also went overboard with custom stuff:
- PDF importers with #ML payee/account prediction
- Custom linters for validation
- Forked #favaEnvelope for envelope budgeting
- #Makefile with 28 targets for price fetching to #FIRE calcs
#plainTextAccounting is great when you can just write #Python to solve your edge cases
#personalFinance #doubleEntryAccounting #CLI #fintech #devlife
Хватит воевать с Makefile: как я написал свой таск-раннер на Rust, чтобы не сойти с ума
Хватит воевать с Makefile: как я написал свой таск-раннер на Rust Устали от табов, .PHONY и bash-лапши? Я тоже. Поэтому написал Nest — декларативный таск-раннер с иерархией, типами и понятным синтаксисом. Рассказываю, как это было и почему вам стоит попробовать.
This crazy document will use #LaTeX for most of it, but #heirloom #doctools for the diagrams. Why? Because I already have a library for #pic and a #Makefile, and I am not afraid to use them. #GraphicsMagick seems to handle converting #PostScript to EPS better than #GhostScript in my situation?! 😕
Hi!
I'm Italo.
I'm going to build my own OpenWRT by mixing repository full of improvements on top of a fork of OpenWRT that uses NSS for thet Dynalink DL-WRX36 (Qualcomm IPQ8072).
Welcome to Jackass.
#SoftrwareDevelopment #OpenWRT #DDWRT #WRT #Router #Routers #Networking #Networks #FOSS #OSS #OpenSource #Git #Makefile #Make #Compilation #Compile #Linux
Progress Bar для Сборки Программы
Компиляцию большой программы можно сравнить с кипячением воды. Вы никогда не можете сказать сколько еще осталось времени до окончания процесса. Многим пользователям GUI-IDE приходится страдать от того, что запустив сборку проекта приходится ждать окончания непредсказуемое время. Однако эту проблему можно решить, если собирать код скриптами сборки. Достоинством сборки проекта из самостоятельно написанных скриптов является то, что в процесс сборки можно добавлять всяческие полезные механизмы. Вы программируете не только свою прошивку, но и процесс сборки самой прошивки. Здорово? В этом тексте я написал про то, как добавить индикатор прогресса в процесс сборки прошивки.
https://habr.com/ru/articles/966248/
#make #gnu_make #progressbar #progress_bar #Makefile #devops #переменные_окружения #компиляция #скрипты_сборки #build_system
Second new: I decided to fully recode "Crisps Chat 🍟" On my opinion - that was a dirty code.
It's a long story, alas...
The recoded version is located here 👉 https://codeberg.org/xolatgames/Crisps-Chat-Recoding
I wish you a nice, and a cool day! ✌️😜
#cpp #cplusplus #app #apps #soft #software #imgui #sdl #sdl2 #messaging #sqlite #sqlite3 #communication #opensource #codeberg #git #cmake #make #makefile #application #applications #linux #DearImGui #messages #chat #chatting #chats
#techpost #C
I really like C and have really leveled up in it.
One of the downsides of C is no namespacing.
But one of my lessons from learning lots of programming languages is
that you can take a good thing from one language and apply it
to another even if it doesn't support it. Typically by adopting
some convention. For example C figuratively does have namespaces
if you are diligent about naming files and functions.
Anyways one of my patterns that I like is that I use a make target like
this:
stuff called "libs". I also have one called "learn". The distinction
is that "libs" is stuff I might re-use, where "learn" is stuff
(like pointer math) that is more of a reference.
So I like this pattern of copying in files from another repo.
And then I just add them to whatever repo locally. It's cool because
it lends itself to developing those libs further in either place.
Like I can re-run that make target to get new changes to
those files, and because they are in git locally, I can see what's
changed. And I can copy the files back to "libs" if the changes
are local. This is a compromise, but very good, especially
since I am learning, so I enjoy the development churn.
Like if I update some code in "libs" it might break something
where I am "importing" it, but then I just fix that up and
commit it all. It's like I don't have to remember, to do
something, because the code breaking will notify me :)
I really like C and have really leveled up in it.
One of the downsides of C is no namespacing.
But one of my lessons from learning lots of programming languages is
that you can take a good thing from one language and apply it
to another even if it doesn't support it. Typically by adopting
some convention. For example C figuratively does have namespaces
if you are diligent about naming files and functions.
Anyways one of my patterns that I like is that I use a make target like
this:
I have a repo of basic C stuff like file handling and binary math
\#makefile target to copy in lib files
libs:
cp ../libs/log/log.[ch] .
stuff called "libs". I also have one called "learn". The distinction
is that "libs" is stuff I might re-use, where "learn" is stuff
(like pointer math) that is more of a reference.
So I like this pattern of copying in files from another repo.
And then I just add them to whatever repo locally. It's cool because
it lends itself to developing those libs further in either place.
Like I can re-run that make target to get new changes to
those files, and because they are in git locally, I can see what's
changed. And I can copy the files back to "libs" if the changes
are local. This is a compromise, but very good, especially
since I am learning, so I enjoy the development churn.
Like if I update some code in "libs" it might break something
where I am "importing" it, but then I just fix that up and
commit it all. It's like I don't have to remember, to do
something, because the code breaking will notify me :)
@koakuma If you are maintaining #makefile by hand, you could just put time utility before every linker and compiler. Piping each command to tee would save your stdout now containing time how long given step took.
Anyway I don't think its really that usefull information, so maybe its better just to track overall #make / #ninjabuild time across changes?
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst