3 ms·
A friend of mine expressed the problem described here in a more formal manner in this paper: http://gittup.org/tup/build_system_rules_and_algorithms.pdf http://
by Bluem00 17y ago
A friend of mine expressed the problem described here in a more formal manner in this paper: http://gittup.org/tup/build_system_rules_and_algorithms.pdf http://gittup.org/tup/build_system_rules_and_algorithms.pdf
He ended up creating his own build system, "tup" < http://gittup.org/tup/ http://gittup.org/tup/ >, based off of it. It also has the property desired in this article that, "No-op builds should be O(1) and instantaneous, and most other builds should be O(WhateverChanged)".
- chadaustin 17y agoThanks for the link! I'll take a look at that and change my strategy accordingly.
- WayneS 17y agotup looks very cool, but I don't see how to fetch the source.
- WayneS 17y agothis seems to work: git clone git://gittup.org/tup.git
- ableal 17y agoThe graph in page 25 is thought-provoking (tup-vs-make on a change-one-of-N files test, N = 1 to 100k). Interesting quote: When a single C file is changed in the 100,000 file case, make can take over half an hour to figure out which file needs to be compiled and linked.