README update

Author: ilg-ul

README-MAINTAINER.md

@@ -410,25 +410,24 @@ location (like
 <https://github.com/xpack-dev-tools/files-cache/tree/master/libs>),
 place them in the XBB cache (`Work/cache`) and restart the build.
 
-### Push the build scripts
-
-- push the `xpack-develop` branch to GitHub
-- possibly push the helper project too
-
-From here it'll be cloned on the production machines.
-
 ## Run the CI build
 
 The automation is provided by GitHub Actions and three self-hosted runners.
 
+### Temporarily disable multi-lib
+
 It is recommended to do **a first run without the multi-libs**
-(see the `defs-source.sh` file), test it,
+(see the `application.sh` file), test it,
 and, when ready, rerun the full build.
 
+### Generate the GitHub workflows
+
 Run the `generate-workflows` to re-generate the
 GitHub workflow files; commit and push if necessary.
 
-- on a permanently running machine (`berry`) open ssh sessions to the build
+### Start the self-hosted runners
+
+- on the development machine (`wksi`) open ssh sessions to the build
 machines (`xbbma`, `xbbli`, `xbbla64` and `xbbla32`):
 
 ```sh
@@ -455,9 +454,16 @@ For `xbbli` & `xbbla64` start two runners:
 ~/actions-runners/xpack-dev-tools/2/run.sh &
 ```
 
-Check that the project is pushed to GitHub.
+### Push the build scripts
+
+- push the `xpack-develop` branch to GitHub
+- possibly push the helper project too
+
+From here it'll be cloned on the production machines.
+
+### Manually trigger the build GitHub Actions
 
-To trigger the GitHub Actions build, use the xPack actions:
+To trigger the GitHub Actions builds, use the xPack actions:
 
 - `trigger-workflow-build-xbbli`
 - `trigger-workflow-build-xbbla64`
@@ -483,13 +489,29 @@ page.
 
 These commands use the `xpack-develop` branch of this repo.
 
+### Re-enable multi-lib
+
+- comment out `XBB_APPLICATION_WITHOUT_MULTILIB` in `application.sh`
+- commit and push the repo
+
+#### Test multilib builds
+
+Multilib builds take too long to run tests on all platforms,
+run them only on the fast machines, like `xbbma` and `xbbli`.
+
+### Manually trigger the multilib build GitHub Actions
+
+To trigger the GitHub Actions builds, use the same xPack actions as before.
+
+## Durations & results
+
 The full builds take about 14 hours (3h30 without multilib):
 
 - `xbbmi`: 6h20 (1h00)
-- `xbbma`: 2h41 (23m)
-- `xbbli`: 3h30 (3h30 Linux, 3h30 Windows; without multi-lib: 37m Linux, 33m Windows)
-- `xbbla64`: 12h51 (3h27)
-- `xbbla32`: 13h30 (3h20)
+- `xbbma`: 2h22 (23m)
+- `xbbli`: 5h00 (2h40 Linux, 0h44 Windows; without multi-lib: 37m Linux, 33m Windows)
+- `xbbla64`: 13h33 (3h30)
+- `xbbla32`: 14h00 (3h15)
 
 The workflows results and logs are available from the
 [Actions](https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/actions/) page.