G. Fowler, "A Case for make", Software - Practice & Experience, vol. 20, no. S1, pp. S1/35-S1/46 (1990).  Home/Search   Document Details and Download   Summary   Related Articles

....In short, it does only what was claimed for it. 6. 2 The make oids and allied developments The shortcomings of make have been addressed (mostly in make s original spirit of pragmatism) in several ways: make oids: many have re implemented it in the hope of providing a popular successor; Fowler [Fowl90] seems to have succeeded, after a false start [Fowl85] bolt ons: these typically address one of two main issues: version selection; automatic dependency extraction; generalisations, especially to support concurrent building (typically, this is advantageous only in local area networks, or ....

....the dependencies were visible to make. Most concurrent make oids (i. e sequential make oids which spawn several compilations concurrently) rely on explicit user defined annotation of the make rules to indicate potential safe concurrency: these include DYNIX make [Sequ87] pmake [Baal88] and nmake [Fowl90], and it would be better if: compilations were not invoked within a public namespace (they may unwantedly overwrite each other s intermediate and output files) each make oid sufficiently understood the actions and their interdependencies so as to be able to schedule them safely and optimally ....

G. Fowler, "A Case for make", Software - Practice & Experience, vol. 20, no. S1, pp. S1/35-S1/46 (1990).

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC