aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/docs/windows.md
diff options
context:
space:
mode:
authorGravatar pcloudy <pcloudy@google.com>2018-04-12 05:34:52 -0700
committerGravatar Copybara-Service <copybara-piper@google.com>2018-04-12 05:35:59 -0700
commitdd2b52b658b37652333df12f787de4c6f0a0be1a (patch)
tree7dbdafc8b4fe9192e2c4fb9d6d966247eef7b11c /site/docs/windows.md
parent2e543610b4615a9a2072bf28bbb681d75f60d6dc (diff)
The alwayslink issue with VS 2017 has been reported and fixed by VS team.
Now there isn't any known issue with Bazel working with VS 2017. RELNOTES: None PiperOrigin-RevId: 192596171
Diffstat (limited to 'site/docs/windows.md')
-rw-r--r--site/docs/windows.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/site/docs/windows.md b/site/docs/windows.md
index 1b7319ac39..dba7677320 100644
--- a/site/docs/windows.md
+++ b/site/docs/windows.md
@@ -125,9 +125,10 @@ To build C++ targets, you need:
* Install the [Visual C++ Build
Tools 2015 or later](http://landinghub.visualstudio.com/visual-cpp-build-tools).
- Due to a [known issue](https://github.com/bazelbuild/bazel/issues/3949) with
- Bazel's support for the Build Tools for Visual Studio 2017, we currently
- recommend using the 2015 version instead.
+ If [alwayslink](be/c-cpp.html#cc_library.alwayslink) doesn't work with
+ VS 2017, that is due to a
+ [known issue](https://github.com/bazelbuild/bazel/issues/3949),
+ please upgrade your VS 2017 to the latest version.
* The `BAZEL_VS` or `BAZEL_VC` environment variable.