Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site cmu-cs-edu2.ARPA Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!mtunh!mtung!mtunf!ariel!vax135!timeinc!phri!pesnta!amd!vecpyr!lll-crg!gymble!umcp-cs!seismo!rochester!cmu-cs-pt!cmu-cs-edu2!hua From: hua@cmu-cs-edu2.ARPA (Ernest Hua) Newsgroups: net.unix-wizards Subject: source file interdependencies Message-ID: <209@cmu-cs-edu2.ARPA> Date: Sun, 30-Jun-85 02:52:09 EDT Article-I.D.: cmu-cs-e.209 Posted: Sun Jun 30 02:52:09 1985 Date-Received: Wed, 3-Jul-85 08:23:50 EDT Organization: Carnegie-Mellon University, CS/RI Lines: 28 ___________________________________________________________________________ Got another question for y'all wizards out there ... Are there utilities (perhaps "make" improvements) that take into account source file dependencies that sit in several places (some possibly in libraries). I have several programs that depend upon quite a few object files and each of them reside in a separate directory that could be moved at any time. I tried placing the common subroutines in libraries, but I could not figure out how to detect a revised library and recompile all dependent programs. It comes down to this: If I revise a particular source file, how do I systematically find all programs dependent upon the corresponding object file without resorting to some sledgehammer manual hack of sorts? Some examples of "sledgehammer manual hacks": - A single cover-everything makefile. - Using "find" to search through all makefiles and to examine all "#includes". All solutions are GREATLY APPRECIATED! ___________________________________________________________________________ Live long and prosper. Keebler { hua@cmu-cs-gandalf }