Provide mechanism to track library dependencies

Now, ar/lib rules can list static libraries or other .d files. These (as well as
the target library) are written to a file called $lib.d. link/exe rules can list
these .d files, causing them to be flattened into an RSP file and appear on the
command line as @$rsp.

The rule to generate the dependency list files depends on the libraries they
contain, so they also act as a stamp file for the dependencies. This gives us
dependency management for free.

1 files changed, 22 insertions, 4 deletions

diff --git a/ninja.rc b/ninja.rc
index 0733e2d3..d1f3550b 100644
--- a/ninja.rc
+++ b/ninja.rc
@@ -74,24 +74,42 @@ fn cc {
 }
 
 fn link {
-	out='$outdir'/$1 objs=() {
+	out='$outdir'/$1 objs=() deps=() {
 		shift
 		for(obj in $*) {
 			if(! ~ $obj '$'*) obj='$outdir'/$obj
-			objs=($objs $obj)
+			switch($obj) {
+			case *.d
+				deps=($deps $obj)
+			case *
+				objs=($objs $obj)
+			}
+		}
+		if(! ~ $#deps 0) {
+			build $out.rsp awk $deps '|' scripts/rsp.awk ; with expr '-f scripts/rsp.awk'
+			objs=($objs '|' $out.rsp)
 		}
 		build $out link $objs
+		if(! ~ $#deps 0)
+			with ldlibs @$out.rsp
+		status=()
 	}
 }
 
 fn ar {
-	out='$outdir'/$1 objs=() {
+	out='$outdir'/$1 objs=() deps=() {
 		shift
 		for(obj in $*) {
 			if(! ~ $obj '$'*) obj='$outdir'/$obj
-			objs=($objs $obj)
+			switch($obj) {
+			case *.[ad]
+				deps=($deps $obj)
+			case *
+				objs=($objs $obj)
+			}
 		}
 		build $out ar $objs
+		build $out.d lines $out $deps
 	}
 }