Update docs since bazel doesn't link agains msys-2.0.dll anymore
RELNOTES: None.
@@ -22,10 +22,6 @@ export JAVA_HOME="$(ls -d C:/Program\ Files/Java/jdk* | sort | tail -n 1)"
export BAZEL_SH=c:/msys64/usr/bin/bash.exe
```
-If you run outside of `bash`, ensure that ``msys-2.0.dll`` is in your ``PATH``
-(if you install msys2 to ``c:\msys64``, just add
-``c:\msys64\usr\bin`` to ``PATH``).
-
If you have another tool that vendors msys2 (such as msysgit), then
``c:\msys64\usr\bin`` must appear in your ``PATH`` *before* entries for
those tools.
@@ -36,27 +32,15 @@ should make sure ``c:\msys64\usr\bin`` appears in ``PATH`` *before*
``c:\windows\system32``, because otherwise Windows' ``bash.exe`` is used before
msys2's.
-Use ``where msys-2.0.dll`` to ensure your ``PATH`` is set up correctly.
-
To **run** Bazel (even pre-built binaries), you will need:
-* Java JDK 8 or later
-* [msys2 shell](https://msys2.github.io/) (need to be installed at
- ``C:\msys64\``).
- * We build against version
- [20160205](https://sourceforge.net/projects/msys2/files/Base/x86_64/msys2-x86_64-20160205.exe/download),
- you will need this version in order to run the pre-built
- [release Bazel binaries](https://github.com/bazelbuild/bazel/releases).
- * You can also use newer versions or the
- [latest version](https://sourceforge.net/projects/msys2/files/latest/download?source=files),
- but then you will need to compile Bazel from the distribution archive (the
- source zip file) so that it's linked against the right version of
- ``msys-2.0.dll``. See also the
- [known issues](install-compile-source.md#known-issues-when-compiling-from-source).
+* Java JDK 8 or later.
+* Python 2.7 or later.
+* [msys2 shell](https://msys2.github.io/).
* Several msys2 packages. Use the ``pacman`` command to install them:
```
- pacman -Syuu gcc git curl zip unzip zlib-devel
+ pacman -Syuu git curl zip unzip
```
## <a name="install"></a>Installation
