diff options
| author |  Yun Peng <pcloudy@google.com> | 2018-03-22 02:43:01 -0700 |
|---|---|---|
| committer |  Copybara-Service <copybara-piper@google.com> | 2018-03-22 02:44:11 -0700 |
| commit | 7cca5d788da153acff59bba19617fc65e468201b (patch) | |
| tree | cb819bfb6181bc86e934f59b4f483f6fffb28888 /site/docs/windows.md | |
| parent | 289a5cbccc2ad880021400825d22b7c1f298545e (diff) | |
Windows doc: Update docs about building Java and Python on Windows
Now we are using the native launcher to run binary for Java and Python,
so the outputs of these targets have changed.
Closes #4898.
Change-Id: Id2ea33d7c02b5608215b5cd4173ed917df0cb217
PiperOrigin-RevId: 190037369
Diffstat (limited to 'site/docs/windows.md')
| -rw-r--r-- | site/docs/windows.md | 17 |
1 files changed, 7 insertions, 10 deletions
diff --git a/site/docs/windows.md b/site/docs/windows.md index a3db04a1d2..1b7319ac39 100644 --- a/site/docs/windows.md +++ b/site/docs/windows.md @@ -172,13 +172,10 @@ C:\projects\bazel> bazel-bin\examples\cpp\hello-world.exe There's no setup necessary. -On Windows, Bazel builds three output files for `java_binary` rules: +On Windows, Bazel builds two output files for `java_binary` rules: * a `.jar` file -* a shell script that can set up the environment for the JVM and run the - binary -* a `.cmd` file (a batch script) that can call Bash with the aforementioned - shell script. +* a `.exe` file that can set up the environment for the JVM and run the binary Try building a target from one of our [sample projects](https://github.com/bazelbuild/bazel/tree/master/examples): @@ -186,7 +183,7 @@ projects](https://github.com/bazelbuild/bazel/tree/master/examples): ``` C:\projects\bazel> bazel build //examples/java-native/src/main/java/com/example/myproject:hello-world -C:\projects\bazel> bazel-bin\examples\java-native\src\main\java\com\example\myproject\hello-world.cmd +C:\projects\bazel> bazel-bin\examples\java-native\src\main\java\com\example\myproject\hello-world.exe ``` ### Build Python @@ -213,10 +210,10 @@ To build Python targets, you need: On Windows, Bazel builds two output files for `py_binary` rules: * a self-extracting zip file -* a batch script that can execute the Python interpreter with the +* an executable file that can launch the Python interpreter with the self-extracting zip file as the argument -You can either run the batch script (it has a `.cmd` extension) or you can run +You can either run the executable file (it has a `.exe` extension) or you can run Python with the self-extracting zip file as the argument. Try building a target from one of our [sample @@ -225,9 +222,9 @@ projects](https://github.com/bazelbuild/bazel/tree/master/examples): ``` C:\projects\bazel> bazel build //examples/py_native:bin -C:\projects\bazel> bazel-bin\examples\py_native\bin.cmd +C:\projects\bazel> bazel-bin\examples\py_native\bin.exe -C:\projects\bazel> python bazel-bin\examples\py_native\bin +C:\projects\bazel> python bazel-bin\examples\py_native\bin.zip ``` If you are interested in details about how Bazel builds Python targets on |