OmniMancer has quit [Read error: Connection reset by peer]
OmniMancer has joined ##openfpga
jfcaron has quit [Ping timeout: 260 seconds]
Asu has quit [Quit: Konversation terminated!]
<pie_[bnc]>
azonenberg: idk if youre still doing build systems stuff but you might be interested in the build systems a la carte : theory and pratice, or the shorter older version of the paper
<q3k>
i like that excel is presented as a build system
<mwk>
... I mean, with sufficient hackery
<q3k>
i mean, in a purely theoretical way
<mwk>
... now I want to make an actual build system out of excel
<q3k>
still better than make
<kc8apf>
Sisyphus was a "build system" at Google that was literally just a way to write step-by-step instructions and let someone walk through them and acknowledge each step
<q3k>
kc8apf: but calling it a build system is pretty generous
<q3k>
kc8apf: it was more of a glorified bash script with save states and a gating API
<q3k>
kc8apf: there was, as far as i know, not really any concept of dependency graphs, other than 'for step A to run, steps B, C and D must have already completed'
<kc8apf>
that describes many build systems I've seen
<qu1j0t3>
isn't that a dependency graph? :)
<q3k>
uh
<q3k>
i mean, technically, yes, but not really in how most build systems treat them
<qu1j0t3>
sure, i understand make and toposort. :)
<q3k>
even with make you dpened on an artifact being present, and you define steps that declare how this artifact is achieved
<q3k>
in this case it was dependency on 'this "command" must've run and not returned an error code'
<kc8apf>
bitbake only depends on a record that previous steps were done
<kc8apf>
it has no notion of artifacts
edmund_ has quit [Ping timeout: 256 seconds]
<pie_[bnc]>
free your mind
<pie_[bnc]>
sideeffects are ephemeral
<qu1j0t3>
pie_[bnc]: The side-effects of whatever you're smoking aren't