aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorRobert Schumacher <roschuma@microsoft.com>2017-10-23 12:15:01 -0700
committerGitHub <noreply@github.com>2017-10-23 12:15:01 -0700
commit65fa778cf62bcd5794b5a24edd867a7e7f1298d8 (patch)
treef29657eea1fe5c6c3d46f2da37996285ccb019d9 /docs
parentf24c1c6ccd8617246d395be1d58abf3dfffcc931 (diff)
parent0b6e08b14823a78c21733bd1a370d60a67b91db1 (diff)
downloadvcpkg-65fa778cf62bcd5794b5a24edd867a7e7f1298d8.tar.gz
vcpkg-65fa778cf62bcd5794b5a24edd867a7e7f1298d8.zip
Merge branch 'master' into master
Diffstat (limited to 'docs')
-rw-r--r--docs/about/faq.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/about/faq.md b/docs/about/faq.md
index 88f88bad0..cb711e384 100644
--- a/docs/about/faq.md
+++ b/docs/about/faq.md
@@ -78,7 +78,7 @@ Vcpkg uses CMake internally as a build scripting language. This is because CMake
## Will Vcpkg support downloading compiled binaries from a public or private server?
We would like to eventually support downloading precompiled binaries, similar to other system package managers.
-In a corporate scenario, we currently recommend building the libraries once and distributing the entire vcpkg root directory to everyone else on the project through some raw file transport such as a network share or HTTP host. See [the `export` command](../users/integration.md#export).
+In a corporate scenario, we currently recommend building the libraries once and distributing the entire vcpkg root directory to everyone else on the project through some raw file transport such as a network share or HTTP host. See the [`export`](../users/integration.md#export) command.
## What Visual C++ toolsets are supported?
We support Visual Studio 2015 Update 3 and above.