Configuration

act needs some configuration to work properly. It looks for a config file called act.conf in the current working directory (or, if you provide -config FILENAME, that path instead). This page describes that file.

Note: each act subcommand also takes various command-line arguments; see each subcommand's documentation, and the standard flags, for details.

The example file

act's source distribution contains a documented example file at bin/act.conf.example.

General syntax

• The configuration file consists of multiple items, each of which is either a line of configuration or a brace-delimited, named block.
• # is the comment character, and discards up to the end of the line.
• Lines containing only whitespace/comments are ignored.

Blocks

Main configuration

machine: set up a machine

The machine ID { ... } block tells act about a machine on which it can run compilers.

compiler: set up a compiler

The compiler ID { ... } block tells act about a compiler it can use. act uses compiler blocks both for running compiler tests, and also to compile single files in other modes.

Helper programs

cpp: configure the C preprocessor

The cpp { ... } block tells act how to run the C preprocessor. act uses the C preprocessor whenever it needs to read a (non-Litmus) C program.

herd: configure the Herd memory model simulator

The herd { ... } block tells herd how to run the Herd memory model simulator. act uses Herd in test mode to compare C program state sets with their compiled assembly equivalents.