diff options
| -rw-r--r-- | BOOTSTRAP-MINGW.cli | 8 | ||||
| -rw-r--r-- | BOOTSTRAP-MSVC.cli | 8 | ||||
| -rw-r--r-- | BOOTSTRAP-UNIX.cli | 6 |
3 files changed, 19 insertions, 3 deletions
diff --git a/BOOTSTRAP-MINGW.cli b/BOOTSTRAP-MINGW.cli index 8495dc7..13f5969 100644 --- a/BOOTSTRAP-MINGW.cli +++ b/BOOTSTRAP-MINGW.cli @@ -40,7 +40,9 @@ use just \c{g++} for the compiler: Note also that at about half way through (\c{bpkg fetch} at step 4 below) the script will stop and prompt you to verify the authenticity of the repository -certificate. +certificate. To run the script unattended you can specify the repository +fingerprint as a second argument, after the installation directory (see +\c{build-mingw.bat /?} for details). The end result of the bootstrap process (performed either with the script or manually) is the installed toolchain as well as the \c{bpkg} configuration in @@ -52,6 +54,10 @@ versions. It can also be used to uninstall the toolchain: > bpkg uninstall build2 bpkg \ +Note also that in both cases (manual or scripted bootstrap), if something +goes wrong and you need to restart the process, you \b{must} start with a +clean toolchain source by unpacking it afresh from the archive. + The rest of this section outlines the manual bootstrap process. \dl| diff --git a/BOOTSTRAP-MSVC.cli b/BOOTSTRAP-MSVC.cli index e30b003..f1ed0e9 100644 --- a/BOOTSTRAP-MSVC.cli +++ b/BOOTSTRAP-MSVC.cli @@ -29,7 +29,9 @@ prompt) like this: Note also that at about half way through (\c{bpkg fetch} at step 4 below) the script will stop and prompt you to verify the authenticity of the repository -certificate. +certificate. To run the script unattended you can specify the repository +fingerprint as a second argument, after the installation directory (see +\c{build-msvc.bat /?} for details). The end result of the bootstrap process (performed either with the script or manually) is the installed toolchain as well as the \c{bpkg} configuration in @@ -41,6 +43,10 @@ versions. It can also be used to uninstall the toolchain: > bpkg uninstall build2 bpkg \ +Note also that in both cases (manual or scripted bootstrap), if something +goes wrong and you need to restart the process, you \b{must} start with a +clean toolchain source by unpacking it afresh from the archive. + The rest of this section outlines the manual bootstrap process. \dl| diff --git a/BOOTSTRAP-UNIX.cli b/BOOTSTRAP-UNIX.cli index 9923316..5879a33 100644 --- a/BOOTSTRAP-UNIX.cli +++ b/BOOTSTRAP-UNIX.cli @@ -83,7 +83,7 @@ $ ./build.sh --install-dir /opt/build2 --sudo sudo clang++ Note also that at about half way through (\c{bpkg fetch} at step 4 below) the script will stop and prompt you to verify the authenticity of the repository certificate. To run the script unattended you can specify the certificate -fingerprint with the \c{--trust} option. +fingerprint with the \c{--trust} option (see \c{build.sh -h} for details). The end result of the bootstrap process (performed either with the script or manually) is the installed toolchain as well as the \c{bpkg} configuration in @@ -95,6 +95,10 @@ $ cd build2-toolchain-X.Y $ bpkg uninstall build2 bpkg \ +Note also that in both cases (manual or scripted bootstrap), if something +goes wrong and you need to restart the process, you \b{must} start with a +clean toolchain source by unpacking it afresh from the archive. + The rest of this section outlines the manual bootstrap process. \dl| |