2018-12-13 01:22:16 +08:00
|
|
|
## Environment and Configuration
|
|
|
|
|
|
|
|
|
|
### Environment Variables
|
|
|
|
|
|
|
|
|
|
#### VCPKG_DOWNLOADS
|
|
|
|
|
|
|
|
|
|
This environment variable can be set to an existing directory to use for storing downloads instead of the internal
|
|
|
|
|
`downloads/` directory. It should always be set to an absolute path.
|
|
|
|
|
|
|
|
|
|
#### VCPKG_FEATURE_FLAGS
|
|
|
|
|
|
|
|
|
|
This environment variable can be set to a comma-separated list of off-by-default features in vcpkg. These features are
|
|
|
|
|
subject to change without notice and should be considered highly unstable.
|
|
|
|
|
|
|
|
|
|
Non-exhaustive list of off-by-default features:
|
|
|
|
|
|
|
|
|
|
- `binarycaching`
|
[vcpkg manifest] Manifest Implementation (#11757)
==== Changes Related to manifests ====
* Add the `manifests` feature flag
* This only says whether we look for a `vcpkg.json` in the cwd, not
whether we support parsing manifests (for ports, for example)
* Changes to the manifests RFC
* `"authors"` -> `"maintainers"`
* `--x-classic-mode` -> `-manifests` \in `vcpkg_feature_flags`
* reserve `"core"` in addition to `"default"`, since that's already
reserved for features
* Add a small helper note about what identifiers must look like
* `<license-string>`: SPDX v3.8 -> v3.9
* `"feature"."description"` is allowed to be an array of strings as well
* `"version"` -> `"version-string"` for forward-compat with versions
RFC
* Add the `--feature-flags` option
* Add the ability to turn off feature flags via passing
`-<feature-flag>` to `VCPKG_FEATURE_FLAGS` or `--feature-flags`
* Add CMake toolchain support for manifests
* Requires either:
* a feature flag of `manifests` in either `Env{VCPKG_FEATURE_FLAGS}`
or `VCPKG_FEATURE_FLAGS`
* Passing the `VCPKG_ENABLE_MANIFESTS` option
* The toolchain will install your packages to
`${VCPKG_MANIFEST_DIR}/vcpkg_installed`.
* Add MSBuild `vcpkg integrate install` support for manifests
* Requires `VcpkgEnableManifest` to be true
* `vcpkg create` creates a port that has a `vcpkg.json` instead of a
`CONTROL`
* argparse, abseil, 3fd, and avisynthplus ports switched to manifest
from CONTROL
* Add support for `--x-manifest-root`, as well as code for finding it if
not passed
* Add support for parsing manifests!
* Add a filesystem lock!
==== Important Changes which are somewhat unrelated to manifests ====
* Rename `logicexpression.{h,cpp}` to `platform-expression.{h,cpp}`
* Add `PlatformExpression` type which takes the place of the old logic
expression
* Split the parsing of platform expressions from checking whether
they're true or not
* Eagerly parse PlatformExpressions as opposed to leaving them as
strings
* Add checking for feature flag consistency
* i.e., if `-binarycaching` is passed, you shouldn't be passing
`--binarysource`
* Add the `Json::Reader` type which, with the help of user-defined
visitors, converts JSON to your internal type
* VcpkgArgParser: place the switch names into a constant as opposed to
using magic constants
* In general update the parsing code so that this ^ works
* Add `Port-Version` fields to CONTROL files
* This replaces the existing practice of
`Version: <my-version>-<port-version>`
==== Smaller changes ====
* small drive-by cleanups to some CMake
* `${_VCPKG_INSTALLED_DIR}/${VCPKG_TARGET_TRIPLET}` ->
`${CURRENT_INSTALLED_DIR}`
* Remove `-analyze` when compiling with clang-cl, since that's not a
supported flag (vcpkg's build system)
* Add a message about which compiler is detected by vcpkg's build
system machinery
* Fix `Expected::then`
* Convert `""` to `{}` for `std::string` and `fs::path`, to avoid a
`strlen` (additionally, `.empty()` instead of `== ""`, and `.clear()`)
* Add `Strings::strto` which converts strings to numeric types
* Support built-in arrays and `StringView` for `Strings::join`
* Add `operator<` and friends to `StringView`
* Add `substr` to `StringView`
* SourceParagraphParser gets some new errors
2020-07-01 01:40:18 +08:00
|
|
|
- `manifest`
|
2018-12-13 01:22:16 +08:00
|
|
|
|
|
|
|
|
#### EDITOR
|
|
|
|
|
|
|
|
|
|
This environment variable can be set to the full path of an executable to be used for `vcpkg edit`. Please see
|
|
|
|
|
`vcpkg help edit` for command-specific help.
|
|
|
|
|
|
|
|
|
|
#### VCPKG_ROOT
|
|
|
|
|
|
|
|
|
|
This environment variable can be set to a directory to use as the root of the vcpkg instance. Note that mixing vcpkg
|
|
|
|
|
repo versions and executable versions can cause issues.
|
|
|
|
|
|
2019-02-26 05:25:27 +08:00
|
|
|
#### VCPKG_VISUAL_STUDIO_PATH
|
2018-12-13 01:22:16 +08:00
|
|
|
|
|
|
|
|
This environment variable can be set to the full path to a Visual Studio instance on the machine. This Visual Studio instance
|
|
|
|
|
will be used if the triplet does not override it via the [`VCPKG_VISUAL_STUDIO_PATH` triplet setting](triplets.md#VCPKG_VISUAL_STUDIO_PATH).
|
|
|
|
|
|
|
|
|
|
Example: `D:\2017`
|
|
|
|
|
|
|
|
|
|
#### VCPKG_DEFAULT_TRIPLET
|
|
|
|
|
|
|
|
|
|
This environment variable can be set to a triplet name which will be used for unqualified triplet references in command lines.
|
|
|
|
|
|
|
|
|
|
#### VCPKG_FORCE_SYSTEM_BINARIES
|
|
|
|
|
|
|
|
|
|
This environment variable, if set, suppresses the downloading of CMake and Ninja and forces the use of the system binaries.
|
2019-03-29 05:34:26 +08:00
|
|
|
|
|
|
|
|
### VCPKG_KEEP_ENV_VARS
|
|
|
|
|
|
|
|
|
|
This environment variable can be set to a list of environment variables, separated by `;`, which will be propagated to
|
|
|
|
|
the build environment.
|
|
|
|
|
|
|
|
|
|
Example: `FOO_SDK_DIR;BAR_SDK_DIR`
|