aboutsummaryrefslogtreecommitdiff
path: root/BOOTSTRAP-MINGW.cli
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2016-09-03 17:27:33 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2016-09-03 17:27:33 +0200
commit879d7e92d823c9dfe6fb3691541f30b662f2a510 (patch)
tree7b4705029c81f2b5decc16cc63cfc1a88e5c7ff3 /BOOTSTRAP-MINGW.cli
parent8622308eefe9a1d63bb4128548260d0ba3d50d7a (diff)
First take on new installation and upgrade instructions
Diffstat (limited to 'BOOTSTRAP-MINGW.cli')
-rw-r--r--BOOTSTRAP-MINGW.cli27
1 files changed, 27 insertions, 0 deletions
diff --git a/BOOTSTRAP-MINGW.cli b/BOOTSTRAP-MINGW.cli
new file mode 100644
index 0000000..75a1c49
--- /dev/null
+++ b/BOOTSTRAP-MINGW.cli
@@ -0,0 +1,27 @@
+// file : BOOTSTRAP-MINGW.cli
+// copyright : Copyright (c) 2014-2016 Code Synthesis Ltd
+// license : MIT; see accompanying LICENSE file
+
+"
+Continuing with Windows Bootstrap, to build with MinGW you can either perform
+the following steps manually or, if you are happy with using the defaults, run
+the \c{build-mingw.bat} batch file. It performs (and echoes) the same set of
+steps as outline below but only allows you to customization the compiler and
+installation directory (run \c{build-mingw.bat /?} for usage) and you can also
+specify an alternative package repository with the \c{BUILD2_REPO} environment
+variable.
+
+For example, if your MinGW distribution is in \c{C:\\mingw\\}, then you could
+run it (from the command prompt that we have started earlier) like this:
+
+\
+> build-mingw.bat C:\mingw\bin\g++
+\
+
+If you are using the \c{build2-mingw} package then you should be able to
+use just \c{g++} for the compiler:
+
+\
+> build-mingw.bat g++
+\
+"