aboutsummaryrefslogtreecommitdiff
path: root/BOOTSTRAP-MSVC.cli
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2017-10-20 16:47:38 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2017-10-20 16:47:38 +0200
commit4e7b8b10ec284e4a381d1aff031137b8a4ac58ed (patch)
tree0e3cc019f296767e43eb397f6e52ea583776f5f7 /BOOTSTRAP-MSVC.cli
parenteb55f9b9b5df5678df0b30f4a0af9f35fcbc4be4 (diff)
Update installation instructions with GNU make bootstrap
Diffstat (limited to 'BOOTSTRAP-MSVC.cli')
-rw-r--r--BOOTSTRAP-MSVC.cli11
1 files changed, 5 insertions, 6 deletions
diff --git a/BOOTSTRAP-MSVC.cli b/BOOTSTRAP-MSVC.cli
index f1ed0e9..ad4f05f 100644
--- a/BOOTSTRAP-MSVC.cli
+++ b/BOOTSTRAP-MSVC.cli
@@ -16,9 +16,8 @@ you are on 64-bit Windows or \"x86 Native Tools Command Prompt\" if you are on
To build with MSVC you can either perform the following steps manually or, if
after reviewing the steps you are happy with using the defaults, run the
\c{build-msvc.bat} batch file. It performs (and echoes) the same set of steps
-as outlined below but only allows you to customize the installation
-directory (run \c{build-msvc.bat /?} for usage). You can also specify an
-alternative package repository with the \c{BUILD2_REPO} environment variable.
+as outlined below but only allows you to customize the installation directory
+and a few other things (run \c{build-msvc.bat /?} for usage).
For example, you could run this batch file (from the above-mentioned command
prompt) like this:
@@ -29,9 +28,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. 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).
+certificate. To run the script unattended you can specify the certificate
+fingerprint with the \c{--trust} option (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