summaryrefslogtreecommitdiff
path: root/lib/Makefile
AgeCommit message (Collapse)Author
2010-01-06Makefiles: Use .DEFAULT to support arbitrary targets from sub directories.Carl Worth
Taking advantage of the .DEFAULT construct means that we won't need to explicitly list targets such as "clean", etc. in each sub-Makefile.
2009-11-12Use $(MAKE) when invoking make from make.Carl Worth
Without this, things like MAKEFLAGS=-j4 can't work.
2009-11-10Implement a non-recursive make.Carl Worth
The idea here is that every Makefile at each lower level will be an identical, tiny file that simply defers to a top-level make. Meanwhile, the Makefile.local file at each level is a Makefile snippet to be included at the top-level into a large, flat Makefile. As such, it needs to define its rules with the entire relative directory to each file, (typically in $(dir)). The local files can also append to variables such as SRCS and CLEAN for files to be analyzed for dependencies and to be cleaned.