diff options
| author | Darío Hereñú <magallania@gmail.com> | 2017-10-21 22:39:01 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-21 22:39:01 +0200 |
| commit | fe842b31d411ed3c14117ca77b65997e671d3a17 (patch) | |
| tree | 2c4c9f77a8aa7479bacd1b4168092cd91881bfbd /docs | |
| parent | 3c89015da2711dce5c96e39be66aa86c2c8ee6a1 (diff) | |
| download | vcpkg-fe842b31d411ed3c14117ca77b65997e671d3a17.tar.gz vcpkg-fe842b31d411ed3c14117ca77b65997e671d3a17.zip | |
Minor fix
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/about/faq.md | 2 |
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. |