CIRCLE WITH A DOT

@cararemixed @1password probably the biggest challenge right now is delivering high-assurance release builds for multiple platforms. it's happening but it is taking quite a bit of effort to build that infrastructure (and associated things like signing with an HSM) on top of Codeberg

@cararemixed @1password slowly but steadily we're progressing towards the first release

@arcterus @aismallard aaa

@recursive ninja files are basically what makefiles should have been, easily parsable, mostly declarative dependency graph descriptions without the bewildering mass of features that accumulates if you also try to shoehorn an UI into it

@recursive oh yeah ninja is excellent. not just the software but the specification, which is one of the few emergent ones that are just good somehow

@recursive my solution to this was to use kati, google's make with a ninja backend

technically this probably caused some sort of staleness somewhere in the system but it was so much faster when i needed rapid iteration that it was totally worth it

@dequbed I haven't used shake but I did use ocamlbuild and the other thing I forget the name of, and it was somewhat preferable to some of the makefiles

dune (a declarative ocaml build system) is way better though

@noisytoot i think it was trying to grep itself but without hitting the grep call, or something similarly unhinged

every time you run make it executes so many $(shell) calls (there are 40 of them, though some would be ifeq'd out) that it takes more time to create a dependency graph than to incrementally compile and link one compilation unit*

* if you use lld and split-dwarf, but still

to be clear i'm not doing this because i love writing cmake syntax that would drive mere mortals mad. i do it because i'm replacing a "simple Makefile" that has perhaps once fit that bill, but eventually turned into a 1200-line (not including *.inc files) monstrosity with a load-bearing rot13 call inside of a manual reimplementation of half of git submodule

(this particular monstrosity has since been removed but the overall genre has not changed)

@x42 in something like 2019 i tried to improve the "simple makefile" that this project used to have and it damn near gave me a psychotic break after i stared at it for three days. believe me, meta-cmake is an improvement

@solonovamax the meme i'm obliquely referencing was about GoT red wedding

hasn't read the book / has read the book

i'm making it sound more complicated than it is, the actual thing boils down to "cmake's dependency resolution algorithm doesn't work for a particular edge case i'm having, so i'm implementing a different one, in cmake script"

but also "dependency resolution algorithm" is basically what a build system is, so,

current status: writing a build system in cmake

not "something that builds a project and is also implemented in implemented in cmake"

no, it is "something that is implemented in cmake and can be used to implement a build system that is in turn used as a part of a build system (also in cmake)"

@0xabad1dea @hypha and if it's creepy you were doing creeptography all along

@david_chisnall hey. Cats have a concept of consequences. We just ignore them

@polarweasel not yet

@joandaro exactly

@Haste two can play that game!