Abstract

The make command has been a central part of the UNIX* programming environment for over fifteen years. An excellent example of a UNIX system software tool, it has a simple model and delegates most of its work to other commands. By dealing with general relationships between files and commands, make easily adapts to diverse applications. This generality, however, has become a handicap when compared with specialized integrated programming environments. Integrated environments are collections of tightly coupled (seamless) programs that can take advantage of programming language details not available to the loosely coupled (tool-based) make model. There are limitations to both approaches, but it would seem that the make model, at least for software construction, is reaching the breaking point. make can be revitalized by abandoning restrictive implementation details and by extending the basic model to meet modern software construction demands. This paper explores these demands and changes an...

Citations

19	Make — A Program for Maintaining Computer - Feldman - 1978
18	The fourth generation make - Fowler - 1985
8	Build---A Software Construction Tool - Erickson, Pellegrin - 1984
8	Mk: A successor to make - Hume - 1987
4	Product Administration through SABLE and nmake - Cichinksi, Fowler - 1988
2	GNU Make -- A Program for Directing Recompilation , Edition 0.1 Beta - Stallman, McGrath - 1989
1	The Odin System: An Object Manager for Extensible Software Environments , Ph.D. thesis and - Clem - 1986
1	A New Dimension for the UNIX Filesystem , this issue - Korn, Krell
1	SunPro: The Sun Programming Environment - Palkovic - 1987
1	Automated Software Management , Software -- Practice and Experience - Waters
1	A True Integrated Environment: CASE Closed - Needs - 1989