Once the development package for Utils has been downloaded, options arise to fully customise a build. They are outlined below.
Utils is designed to work under a variable
name. This is implemented via the
which is part of the GNU Autotools build system. 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 entitled
“configure.ac”. Once the variables are modified,
a command such as:
must be called to generate a fresh
./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
replace placeholders of: “@LIBRARY_NAME@”.
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. When in a terminal navigated to the directory in which Makefile is housed, a command of:
will create such a build.
Utils can be built from a multitude of sources for fully customised builds. Because each module is optional and order-independent, a multiplicity of permutations exist.
For those that prefer a terminal, a builder written in Bash exists. A command such as:
./build.sh [module name] [module name] [module name]
will create a build with three modules.