Global
/
vcpkg
mirror of https://github.com/microsoft/vcpkg.git
1
0
Fork 0
Code Activity

Update versioning.getting-started.md (#18000)

This commit is contained in:
ras0219 2021-05-18 23:15:29 -07:00 committed by GitHub
parent 5554e3f268
commit 3738723dd2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
docs/examples/versioning.getting-started.md
View File

@ -4,42 +4,6 @@
Vcpkg lets you take control of which version of packages to install in your projects using manifests.
## Enabling versions
To start using [versioning](../users/versioning.md), first you need to enable the `versions` feature flag in any of the following manners:
* Setting the `VCPKG_FEATURE_FLAGS` environment variable
```PowerShell
# Example for PowerShell
$env:VCPKG_FEATURE_FLAGS="versions"
```
```bash
# Example for bash
export VCPKG_FEATURE_FLAGS=versions
```
```cmd
REM Example for cmd
SET VCPKG_FEATURE_FLAGS=versions
```
* Passing the feature flags in the vcpkg command line
```bash
./vcpkg install --feature-flags=versions
```
* Setting `VCPKG_FEATURE_FLAGS` before your `project()` CMake directive
```cmake
set(VCPKG_FEATURE_FLAGS versions)
project(myapp)
```
* Setting `VcpkgAdditionalInstallOptions` (Project Properties -> Vcpkg -> Additional Options) in your MSBuild project
```xml
<PropertyGroup>
<VcpkgAdditionalInstallOptions>--feature-flags=versions</VcpkgAdditionalInstallOptions>
</PropertyGroup>
```
## Using versions with manifests
With the `versions` feature flag enabled you can start adding version constraints to your dependencies.