Assume this tree structure
Recusrive make can be used to build everything in the tree. The directory $HOME contains this common.mk file
Each of the subdirectories will contain a Makefile that includes the common.mk. Then running the command make -I$HOME from A gives
Following from the above, each Makefile in subfolders will start by defining its own specific variables, and then it will include a common.mk which resides in common location such as $HOME.
Each makefile will include this file. An example of a Makefile in the A directory shown above is
Each sub directory will include similar makefile which starts by listing the directories below it, then including common.mk
The actions actually performed by makefile will be done at the bottom most directories first, followed by the higher level up. This means the tree is first traveresed to the bottom, then when the bottom is reached, on going back up, each makefile will execute any other action in its all such as compiling files and other such tasks. So, this is like a stack. The last directory visited on the way down, is the first directory that will be updated in the build process, and the top directory, will be the last directory that is updated.
Suppose I have index.tex that I want to build it to index.htm to try something but it is allready update to date. But if I do make clean it will now clean everything down the whole tree, which is not what I want.
I can touch index.tex then do make. But I can also use -B option and give it the target to build, like this
from http://pic.dhe.ibm.com/infocenter/aix/v6r1/ it says
echo -e "lines\ncols"tput -S— ref: this also stty size
Tools for terminal are here
Has make build-in symbols http://www.chemie.fu-berlin.de/chemnet/use/info/make/make_15.html