User:Boyski~enwiki/Audited Objects

Audited Objects, or AO, is an open-source tool for the analysis and optimization of automated software processes such as builds [1]. When a build process is run under AO control, each command executed is recorded in a central database along with a record of each file opened by that command and its state (checksum/size/timestamp) at that instant. A full copy of each modified file is stored in the database as well.

AO also provides a suite of tools for analyzing this data once collected. For example, given a binary file built under AO control a user can determine the complete set of input files which contributed to it, including source files, build scripts, compilers, header files and libraries, etc.

AO is somewhat analogous to the clearmake and clearaudit components of IBM Rational ClearCase while not requiring the special MVFS file system. It offers the same winkin capability as clearmake. Unlike clearmake, however, AO is not itself a build tool. Instead, it injects its build auditing and avoidance capabilities into any build tool.

See Also

• IBM Rational ClearCase
• ccache
• makedepend
• Application lifecycle management

External links

• Audited Objects
• Other dependency-generation schemes