Safeness of Make-Based Incremental Recompilation

Authors:
Niels Jørgensen
Affiliations:
-
Venue:
FME '02 Proceedings of the International Symposium of Formal Methods Europe on Formal Methods - Getting IT Right
Year:
2002

Citing 7
Cited 1

Smart recompilation

ACM Transactions on Programming Languages and Systems (TOPLAS) - The MIT Press scientific computation series
Denotational semantics: a methodology for language development

Denotational semantics: a methodology for language development
The cost of selective recompilation and environment processing

ACM Transactions on Software Engineering and Methodology (TOSEM)
Static interpretation of modules

Proceedings of the fourth ACM SIGPLAN international conference on Functional programming
A greedy concurrent approach to incremental code generation

POPL '85 Proceedings of the 12th ACM SIGACT-SIGPLAN symposium on Principles of programming languages
Incremental evaluation for attribute grammars with application to syntax-directed editors

POPL '81 Proceedings of the 8th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
Managing Projects with Make

Managing Projects with Make

Grexmk: speeding up scripted builds

Proceedings of the 2006 international workshop on Dynamic systems analysis

Quantified Score

Hi-index	0.00

Visualization

Abstract

The make program is widely used in large software projects to reduce compilation time. make skips source files that would have compiled to the same result as in the previous build. (Or so it is hoped.) The crucial issue of safeness of omitting a brute-force build is addressed by defining a semantic model for make. Safeness is shown to hold if a set of criteria are satisfied, including soundness, fairness, and completeness of makefile rules. Conditions are established under which a makefile can safely be modified by deleting, adding, or rewriting rules.