Re:Tup – an instrumenting file-based build system
by agumonkey on Tuesday August 16, 2022 @01:56AM
(#32479618)
I wonder if tup devs are aware and interested in adapting their model to solve the multiple byproduct per file.
Re:Tup – an instrumenting file-based build system
by gonzus on Tuesday August 16, 2022 @05:13AM
(#32480726)
Last time I dabbled with tup, I remember it was not trivial to support any process that generated more than one output. My use case back then was lex / yacc: you can generate a source and a header file with them (and even some other output files), but it was not trivial to capture these dependencies with tup.
Tup fit nicely, until build variants or Java were needed.
Aside from not really working well on Windows, at least at the time, variants were completely broken on Windows.
Further, compiling any Java with inner classes was impossible since they emitted extra class files for each inner class, which meant the build artifact hierarchy depended on the code - something Tup isn't prepared to handle.
It just got really annoying over time.
Ninja-based systems quickly replaced it for me.