1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
|
---
layout: documentation
title: Windows
---
Windows support is highly experimental. Known issues are [marked with
label "Windows"](https://github.com/bazelbuild/bazel/issues?q=is%3Aissue+is%3Aopen+label%3A%22category%3A+multi-platform+%3E+windows%22)
on github issues.
We currently support only 64 bit Windows 7 or higher and we compile Bazel as a msys2 binary.
Using the release binary
=========================
Release binaries are available on our [GitHub release page](https://github.com/bazelbuild/bazel/releases).
To run the binary you will need:
* Java JDK 8 or later
* [msys2](https://msys2.github.io/) (need to be installed at
``C:\tools\msys64\``).
* We build against version
[20160205](https://sourceforge.net/projects/msys2/files/Base/x86_64/msys2-x86_64-20160205.exe/download),
the [newer versions](https://sourceforge.net/projects/msys2/files/latest/download?source=files)
should also work. Older versions are known to have
[issues](https://github.com/bazelbuild/bazel/issues/1919).
Before you run the binary, you will need to set some environment
variables:
```bash
export JAVA_HOME="$(ls -d C:/Program\ Files/Java/jdk* | sort | tail -n 1)"
export BAZEL_SH=c:/tools/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:\tools\msys64``, just add
``c:\tools\msys64\usr\bin`` to ``PATH``).
### Issues/Troubleshooting
If you have another tool that vendors msys2 (such as msysgit), then ``c:\tools\msys64\usr\bin`` must appear in your ``PATH`` *before* entries for those tools.
Similarly, if you have [bash on Ubuntu on Windows](https://msdn.microsoft.com/en-gb/commandline/wsl/about) installed, you should make sure ``c:\tools\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.
Building Bazel on Windows
=========================
To bootstrap Bazel on Windows, you will need:
* Java JDK 8 or later
* [Visual C++](https://www.visualstudio.com/) with Windows SDK installed
(Community Edition is fine)
* [msys2](https://msys2.github.io/) (need to be installed at
``C:\tools\msys64\``).
* Several msys2 packages. Use the ``pacman`` command to install them:
``pacman -Syuu gcc git curl zip unzip zlib-devel``
To build Bazel:
* Open the msys2 shell.
* Clone the Bazel git repository as normal.
* Set the environment variables:
```bash
export JAVA_HOME="$(ls -d C:/Program\ Files/Java/jdk* | sort | tail -n 1)"
export BAZEL_SH=c:/tools/msys64/usr/bin/bash.exe
```
* Run ``compile.sh`` in Bazel directory.
* If all works fine, bazel will be built at ``output\bazel.exe``.
Using Bazel on Windows
======================
Bazel now supports building C++, Java and Python targets on Windows.
### Build C++
To build C++ targets, you will need:
* [Visual Studio](https://www.visualstudio.com/)
<br/>We are using MSVC as the native C++ toolchain, so please ensure you have Visual
Studio installed with the Visual C++ components
(which is NOT the default installation type of Visual Studio).
You can set BAZEL\_VS environment variable to tell Bazel
where Visual Studio is, otherwise Bazel will try to find the latest version installed.
<br/>For example: `export BAZEL_VS="C:/Program Files (x86)/Microsoft Visual Studio 14.0"`
* [Python 2.7](https://www.python.org/downloads/)
<br/>Currently, we use python wrapper scripts to call the actual MSVC compiler, so
please make sure Python is installed and its location is added into PATH.
It's also a good idea to set BAZEL\_PYTHON environment variable to tell Bazel
where python is.
<br/>For example: `export BAZEL_PYTHON=C:/Python27/python.exe`
Bazel will auto-configure the location of Visual Studio and Python at the first
time you build any target.
If you need to auto-configure again, just run `bazel clean` then build a target.
If everything is set up, you can build C++ target now! However, since MSVC
toolchain is not default on Windows yet, you should use flag
`--cpu=x64_windows_msvc` to enable it like this:
```bash
$ bazel build --cpu=x64_windows_msvc examples/cpp:hello-world
$ ./bazel-bin/examples/cpp/hello-world.exe
$ bazel run --cpu=x64_windows_msvc examples/cpp:hello-world
```
### Build Java
Building Java targets works well on Windows, no special configuration is needed.
Just try:
```bash
$ bazel build examples/java-native/src/main/java/com/example/myproject:hello-world
$ ./bazel-bin/examples/java-native/src/main/java/com/example/myproject/hello-world
$ bazel run examples/java-native/src/main/java/com/example/myproject:hello-world
```
### Build Python
On Windows, we build a self-extracting zip file for executable python targets, you can even use
`python ./bazel-bin/path/to/target` to run it in native Windows command line (cmd.exe).
See more details in this [design doc](/designs/2016/09/05/build-python-on-windows.html).
```bash
$ bazel build examples/py_native:bin
$ ./bazel-bin/examples/py_native/bin
$ python ./bazel-bin/examples/py_native/bin # This works in both msys and cmd.exe
$ bazel run examples/py_native:bin
```
|
