Utils is designed to work under a variable
name. This is implemented via the autoconf utility,
which is part of the GNU Autotools build system[0]. This step is
optional, but optimal for demanding scenarios.

In order to generate text in a dynamic fashion,
autoconf is used to plug in templates
and strings as Bash variables. These variables can
be found in a file[1] entitled
“configure.ac”. Once the variables are modified,
a command such as:

Once a ./configure shell script has been generated,
it can be executed. Execution of the script will replace special
placeholders (demarcated by @ characters). For example,
the Bash variable LIBRARY_NAME will
replace placeholders of: “&commat;LIBRARY_NAME&commat;”.
This particular variable is used heavily in Utils to
facilitate fully customised builds.

If Utils has been configured, the Makefile is
the next logical step for pre-defined builds. A build is
provided for the “core”; builds are also provided
for each independent module (prefixed with the
“core”). Finally, a build with every module is
provided. Each of these categories are listed below.

In the “complete” build, all modules are concatenated
in defined order (though independent modules are order-independent
). The build is then formed into a file[2]. When in a terminal
navigated to the directory in which Makefile is housed, a command of: