diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2017-05-03 14:27:57 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2017-05-03 14:27:57 +0200 |
| commit | 29422008cee820069db67d4e02fb2bafae70cbb1 (patch) | |
| tree | 59b037d2d9daff4d9cd61a1981c39defd4b8f703 /INSTALL.cli | |
| parent | 2ac4f45a0bb4b02eb8fe13b96d4afc5cd7154f26 (diff) | |
Update INSTALL
Diffstat (limited to 'INSTALL.cli')
| -rw-r--r-- | INSTALL.cli | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/INSTALL.cli b/INSTALL.cli index c62a3b5..e0785bf 100644 --- a/INSTALL.cli +++ b/INSTALL.cli @@ -25,10 +25,10 @@ the UNIX version of the commands. In this case making a Windows version is a simple matter of adjusting paths and, if used, line continuations. The \c{build2} toolchain requires a C++14 compiler. From the commonly-used -options, GCC 4.8, Clang 3.4, and MSVC 2015/14 Update 2 or any later versions +options, GCC 4.9, Clang 3.4, and MSVC 14 (2015) Update 3 or any later versions of these compilers should work. Note also that the C++ compiler that you use to build the \c{build2} toolchain and the one that you will use to build your -projects need not be the same. For example, if you are using MSVC 2013/12 +projects need not be the same. For example, if you are using MSVC 12 (2013) (which cannot build \c{build2}), it is perfectly fine to get a minimal MinGW toolchain and use that to build \c{build2}; you will still be able to use MSVC to build your own code. |