Run the desired build steps. Normally, Steps is the list below,
optionally prefixed with distclean or clean. [test] may be
omited if --no-test is effective.
[[dependencies], [configure], build, [test], install]
Each step finds an applicable toolchain based on known unique files
and calls the matching plugin to perform the step. A step may fail,
which causes the system to try an alternative. A step that wants to
abort the build process must throw an exception.
If a step fails, a warning message is printed. The message can be
suppressed by enclosing the step in square brackets. Thus, in the
above example of Steps, only failure by the build and install
steps result in warning messages; failure of the other steps is
silent.
The failure of a step can be made into an error by enclosing it
in curly brackets, e.g. [[dependencies], [configure], {build}, [test], {install}]
would throw an exception if either the build or install step failed.
Options are:
- pack_version(N)
- where N is 1 or 2 (default: 1).
This determines the form of environment names that are set before
the build tools are calledd.
For version 1, names such as SWIPLVERSION or SWIHOME are used.
For version 2, names such as SWIPL_VERSION or SWIPL_HOME_DIR are used.
@tbd If no tool is willing to execute some step, the step is
skipped. This is ok for some steps such as dependencies or test.
Possibly we should force the install step to succeed?
