Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[vcpkg docs] Update versioning.getting-started.md #18000

Merged
merged 1 commit into from
May 19, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 0 additions & 36 deletions docs/examples/versioning.getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down