summaryrefslogtreecommitdiffhomepage
path: root/etc
diff options
context:
space:
mode:
authorLucio Andrés Illanes Albornoz <lucio@lucioillanes.de>2020-03-11 17:12:01 +0000
committerLucio Andrés Illanes Albornoz <lucio@lucioillanes.de>2020-03-11 17:12:01 +0000
commited7b28de4ac405fd1da51c2a338f655a21ec0e73 (patch)
treed01f531c32e1497a1cb59e9485a573724684e17a /etc
parentdb79d70a0855615424d832bf3a77819acf233949 (diff)
downloadmidipix_build-ed7b28de4ac405fd1da51c2a338f655a21ec0e73.tar.bz2
midipix_build-ed7b28de4ac405fd1da51c2a338f655a21ec0e73.tar.xz
etc/README.md: updated.
Diffstat (limited to 'etc')
-rw-r--r--etc/README.md19
1 files changed, 10 insertions, 9 deletions
diff --git a/etc/README.md b/etc/README.md
index 4d95db98..31bbaff2 100644
--- a/etc/README.md
+++ b/etc/README.md
@@ -66,7 +66,7 @@ Install the build-time dependencies listed in section [2.1](#21-build-time-depen
clone this repository, and run the following command line:
```shell
-./build.sh -a nt64 -b release -P -v
+./build.sh -a nt64 -b release -D zipdist -P -v
```
By default, the build will take place within ``${HOME}/midipix/nt64/release``
@@ -120,7 +120,7 @@ Extract its contents on the target machine, run ``bash.bat``, and then
``/install.sh`` inside the resulting self-contained Midipix installation shell
window.
-N.B. The pathname of the target directory containing ``bash.bat`` and all other
+> N.B. The pathname of the target directory containing ``bash.bat`` and all other
distribution files must not contain whitespaces.
[Back to top](#table-of-contents)
@@ -161,14 +161,15 @@ needed, or forcibly, respectively:
```
Restart the ``configure``, ``build``, and ``install`` steps of the ``coreutils``
-package.
+package:
```shell
./build.sh -r coreutils:configure,build,install
```
-Rebuild entire build group:
+Rebuild entire build groups including or excluding group dependencies, respectively:
```shell
./build.sh [ ... ] -r ALL native_runtime
+./build.sh [ ... ] -r ALL \*native_runtime
```
[Back to top](#table-of-contents)
@@ -283,10 +284,10 @@ package configuration failed or appears relevant, log the configuration process
in, most usually, ``${PKG_BUILD_DIR}/config.log``.
If ``--dump-on-abort`` was specified, a subset of the variables set and environment
-variables will be written to ``${BUILD_WORKDIR}/${PKG_NAME}.dump`` which may subsequently
+variables will be written to ``${BUILD_WORKDIR}/${PKG_NAME}.dump``, which may subsequently
be used in order to obtain a package build shell environment with ``pkgtool.sh``, e.g.:
-```shell
+```
midipix_build@sandbox:(src/midipix_build)> $ ./pkgtool.sh mc
==> 2020/03/11 15:46:28 Launching shell `/usr/bin/zsh' within package environment and `/home/midipix_build/midipix/nt64/debug/tmp'.
==> 2020/03/11 15:46:28 Run $R to rebuild `mc'.
@@ -299,9 +300,9 @@ Consult sections [3.2](#32-adding-a-package), [3.4](#34-patches-and-vars-files),
[4.1](#41-build-steps), and [4.2](#42-package-variables) for further information
concerning the package build process.
-> N.B. When using ``pkgtool.sh`` on a build w/ build variables (see [4](#4-build-variables))
-overriden on command line or via the environment, ensure that they are included in the
-``pkgtool.sh`` command line or exported.
+> N.B. When using ``pkgtool.sh`` on a build w/ build variables (see section [4](#4-build-variables))
+overriden on the command line or via the environment, ensure that they are included in the
+``pkgtool.sh`` command line or exported, respectively.
[Back to top](#table-of-contents)