|Deletions are marked like this.||Additions are marked like this.|
|Line 31:||Line 31:|
|The list holds the configurable options, each variable can be enabled/disabled by passing '''--enable-'''/'''--disable--'''name during the configure invocation.||The list holds the configurable options, each variable can be enabled/disabled by passing '''--enable-'''/'''--disable-'''''$name'' during the configure invocation.|
The Libav build system is based on posix shell and gnu make and follows the quite common pattern of having a configure script to set options and check the build environment and Makefile rules to implement actions.
Even if the configure script named as the one commonly provided by autotools its syntax is not always compatible.
The configure script is implemented using posix shell in order to ensure optimal portability.
The script could be split in three logic blocks: variable system and test logic and output writer
In the configure script every feature and option is describe as a variable, the variable has a name and a state. Each variable belongs to one or more lists specifying its behaviour.
The state can be enabled, disabled or unset.
When run the script parses its argument and the environment variables, setting the initial state for all the variables .
The components may have dependency relationships and if a required feature depends on a missing component an error is reported.
Upon success the configure script generates a Makefile, c header, asm header and pkgconf files.
The variables are grouped in lists,
The list holds the features that should be probed, such as external library presence or system capabilities.
The list holds the configurable options, each variable can be enabled/disabled by passing --enable-/--disable-$name during the configure invocation.
The configure script provides a simple dsl to express dependencies across components.
The following primitives are available:
All the components in