On 28 March 2017 at 18:48, Pickfire <pickfire_AT_riseup.net> wrote:
> I see tup as a good build system but not used by many.
An interesting feature I noticed was that it automatically detects dependencies.
"The trick is that tup instruments all commands that it executes in
order to determine what files were actually read from (the inputs) and
written to (the outputs). When the C preprocessor opens the header
file, tup will notice that and automatically add the dependency. In
fact, we don't have to specify the C input file either, but you can
leave that in there for now since we'll use it in the next section."
[0]
That seems an interesting feature!?
Ninja does something different in this respect where you as the
build-file writer has to write a rule explicitly to request the
compiler generate the header dependencies. e.g. gcc -MMD -MF out.d [1]
Before being carried away - it seems it's achievable with (GNU?) make
but with significantly more headache [2].
[0]
http://gittup.org/tup/ex_a_first_tupfile.html
[1]
https://ninja-build.org/manual.html#ref_headers
[2]
http://make.mad-scientist.net/papers/advanced-auto-dependency-generation/#basic
--
Tai Chi Minh Ralph Eastwood
tcmreastwood_AT_gmail.com
Received on Wed Mar 29 2017 - 10:53:25 CEST