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
#makefile
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?
And this also happened even with "Cat a shooter πΌ". Now you can use GNU Make, for building this game through the Makefile:
https://codeberg.org/xolatgames/cat-a-shooter
Have a nice day! β
#love2d #lua #arcade #space #spaceinvaders #game #games #gamedev #development #make #makefile #compilation #codeberg #opensource #devlog #buildsystem #2d
And the last one: You can build Birdy π¦ or "Crisps Chat π" through CMake now!
If you don't want to install CodeLite IDE, and set it up for working with these projects, you can use CMake for building these projects now.
More details, and instructions about how to do this, you can find in the projects' repositories:
Birdy π¦: https://codeberg.org/xolatgames/Birdy-wants-crisps
"Crisps Chat π": https://codeberg.org/xolatgames/crisps-chat
#cpp #cplusplus #development #devlog #codeberg #opensource #make #makefile #cmake #compilation
π§ π Been deep in the weeds refining my APA 7 student paper templateβfully accessible, screen reader-friendly, and powered by LaTeX + Makefile automation. Itβs designed for blind students, accessibility advocates, and anyone who wants a clean, reproducible academic workflow. Note that it doesn't use the apa7 class since that wouldn't allow the PDF to be tagged for accessibility.
β Includes:
- Automated PDF builds with BibLaTeX
- Submission and status reporting targets
- Sample references. Bib
- Screen reader-friendly README
Built and tested across Raspberry Pi, Fedora Remix, and openSUSE with WSL integration. If youβre navigating academic publishing with accessibility in mind, I made this for you.
#Accessibility #BlindTech #LaTeX #Makefile #AcademicWriting #OpenSource #WSL #Linux #ScreenReader #DisabilityAdvocacy #TechForGood #APA7 #GitHub #RaspberryPi #FedoraRemix #openSUSE #AcademicWorkflow
ΠΠ΅ΠΊΡΠΎΠΊΠΎΠΌΠΏΠΈΠ»ΡΡΠΈΡ ΠΈΠ»ΠΈ ΠΊΠ°ΠΊ ΡΠΎΠ±ΡΠ°ΡΡ OpenWatcom Π΄Π»Ρ QNX4 ΠΏΠΎΠ΄ Debian 12 ΠΈ ΠΏΡΠΈΠΊΡΡΡΠΈΡΡ Π΅Π³ΠΎ ΠΊ Eclipse
ΠΠ΅Π½Ρ Π·ΠΎΠ²ΡΡ Π―ΡΠΎΡΠ»Π°Π² ΠΠΎΠΌΠ±ΠΎΠ² ΠΈ Ρ Π±ΠΎΠ»Π΅Π΅ 30 Π»Π΅Ρ Π·Π°Π½ΠΈΠΌΠ°ΡΡΡ ΡΠΎΠ·Π΄Π°Π½ΠΈΠ΅ΠΌ ΠΠ‘Π£Π’Π. ΠΠ°ΠΊ Π²Ρ ΠΏΠΎΠ½ΠΈΠΌΠ°Π΅ΡΠ΅ ΠΆΠΈΠ·Π½Π΅Π½Π½ΡΠ΅ ΡΠΈΠΊΠ»Ρ Π² ΠΠ‘Π£Π’Π ΡΡΡΠΊΠ° Π΄Π»ΠΈΡΠ΅Π»ΡΠ½Π°Ρ ΠΈ ΠΈΠ½ΠΎΠ³Π΄Π° Π²ΠΎΠ·Π½ΠΈΠΊΠ°ΡΡ Π·Π°Π΄Π°ΡΠΈ ΡΡΠΎ-ΡΠΎ Π΄ΠΎΠ±Π°Π²ΠΈΡΡ Π² ΡΠΈΡΡΠ΅ΠΌΡ ΡΠ°Π±ΠΎΡΠ°ΡΡΡΡ ΡΠΆΠ΅ Π»Π΅Ρ 20. Π ΠΈΠΌΠ΅Π½Π½ΠΎ ΡΠ°ΠΊΠΎΠΉ ΡΠ»ΡΡΠ°ΠΉ ΠΏΡΠΎΠΈΠ·ΠΎΡΠ΅Π» - Π²ΠΎΠ·Π½ΠΈΠΊΠ»Π° Π½Π΅ΠΎΠ±Ρ ΠΎΠ΄ΠΈΠΌΠΎΡΡΡ ΠΈΠ·ΠΌΠ΅Π½ΠΈΡΡ ΠΊΠΎΠ΄ Π² ΠΊΠΎΠ½ΡΡΠΎΠ»Π»Π΅ΡΠ΅ ΠΏΠΎΠ΄ ΡΠΏΡΠ°Π²Π»Π΅Π½ΠΈΠ΅ΠΌ QNX4. ΠΠΎΠΆΠ½ΠΎ ΠΊΠΎΠ½Π΅ΡΠ½ΠΎ Π±ΡΠ»ΠΎ ΠΏΠΎΠ³ΠΎΠ²ΠΎΡΠΈΡΡ Π½Π° ΡΠ΅ΠΌΡ "Π²Ρ Π² ΠΊΠ°ΠΊΠΎΠΌ ΠΌΠΎΡΠ³Π΅ ΡΡΠΎΠ³ΠΎ Π€ΡΠ°Π½ΠΊΠ΅Π½ΡΡΠ΅ΠΉΠ½Π° ΠΏΠΎΠ»ΡΡΠ°Π»ΠΈ ΡΡΠ΄Π° ΠΈ ΠΎΠ±ΡΠ°ΡΠ°ΠΉΡΠ΅ΡΡ", Π½ΠΎ ΠΏΡΠΈ Π±Π»ΠΈΠΆΠ°ΠΉΡΠ΅ΠΌ ΡΠ°ΡΡΠΌΠΎΡΡΠ΅Π½ΠΈΠΈ ΠΎΠΊΠ°Π·Π°Π»ΠΎΡΡ ΡΡΠΎ ΠΊΠΎΠ΄ ΠΌΠΎΠΉ ΡΠΎΠ±ΡΡΠ²Π΅Π½Π½ΡΠΉ ;). Π‘Π°ΠΌΠΎΠ΅ ΠΏΡΠΎΡΡΠΎΠ΅ ΡΠ΅ΡΠ΅Π½ΠΈΠ΅ ΠΎΡΠΊΡΡΡΡ mcedit, ΡΡΠΎ-ΡΠΎ ΠΏΠΎΠΏΡΠ°Π²ΠΈΡΡ ΠΈ ΡΠΎΠ±ΡΠ°ΡΡ Π² ΡΠ°ΠΌΠΎΠΌ QNX4, Π½ΠΎ Π΄Π»Ρ Π½Π°ΡΠ°Π»Π° Π½Π°Π΄ΠΎ Π²ΡΠΏΠΎΠΌΠ½ΠΈΡΡ ΡΠ°Π·ΠΎΠ±ΡΠ°ΡΡΡΡ ΠΊΠ°ΠΊ Π²ΡΠ΅ ΡΠ°Π±ΠΎΡΠ°Π΅Ρ, Π° ΡΡΠΎ ΡΠ΄ΠΎΠ±Π½Π΅ΠΉ Π΄Π΅Π»Π°ΡΡ Π² ΡΠΎΠ²ΡΠ΅ΠΌΠ΅Π½Π½ΡΡ IDE. ΠΠΎΠΈΡΠΊ Π±ΠΈΠ½Π°ΡΠ½ΠΈΠΊΠΎΠ² OpenWatcom (OW) ΠΏΠΎΠ΄ Π»ΠΈΠ½ΡΠΊΡ Π΄Π°Π» ΡΠΎΠ²Π½ΠΎ Π΄Π²Π° Π°ΡΡ ΠΈΠ²Π° ΠΊΠΎΡΠΎΡΡΠ΅ Π² ΠΌΠΎΠ΅ΠΉ ΡΠΈΡΡΠ΅ΠΌΠ΅ Π½Π΅ Π·Π°ΡΠ°Π±ΠΎΡΠ°Π»ΠΈ. ΠΠΎΡΡΠΎΠΌΡ ΡΠ΅ΡΠ΅Π½ΠΎ Π΄Π΅ΠΉΡΡΠ²ΠΎΠ²Π°ΡΡ ΠΏΠΎ ΠΏΡΠΈΠ½ΡΠΈΠΏΡ - Π»ΡΡΡΠ΅ Π΄Π΅Π½Ρ ΠΏΠΎΡΠ΅ΡΡΡΡ, ΠΏΠΎΡΠΎΠΌ Π·Π° ΠΏΡΡΡ ΠΌΠΈΠ½ΡΡ Π΄ΠΎΠ»Π΅ΡΠ΅ΡΡ. ΠΠΎΠ»Π΅ΡΠ΅Π»ΠΈ
sysadmins, devs, linux weirdos, and cable-management deniers β show me your rigs.
desks, racks, homelabs, tmux grids, the whole mess.
bonus points for blinking lights and bash prompts.
Iβll go first π§βπ»
#Linux #Sysadmin #Homelab #DeskSetup #Battlestation #Unix #tmux #Proxmox #Kubernetes #Talos #Makefile #DevLife #NerdSpace
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst