aboutsummaryrefslogtreecommitdiff
path: root/BOOTSTRAP-MSVC.cli
diff options
context:
space:
mode:
Diffstat (limited to 'BOOTSTRAP-MSVC.cli')
-rw-r--r--BOOTSTRAP-MSVC.cli10
1 files changed, 5 insertions, 5 deletions
diff --git a/BOOTSTRAP-MSVC.cli b/BOOTSTRAP-MSVC.cli
index 7076deb..e1c4104 100644
--- a/BOOTSTRAP-MSVC.cli
+++ b/BOOTSTRAP-MSVC.cli
@@ -26,11 +26,11 @@ prompt) like this:
> .\build-msvc.bat
\
-Note also that at about half way through (\c{bpkg fetch} at step 4 below) the
+\N|Note 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 (see \c{build-msvc.bat /?} for
-details).
+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
@@ -42,9 +42,9 @@ 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.
+\N|Note 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.