<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vcpkg/ports/avisynthplus/CONTROL, branch aws-lambda-cpp</title>
<subtitle>Forked from https://github.com/microsoft/vcpkg</subtitle>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/vcpkg/'/>
<entry>
<title>[vcpkg manifest] Manifest Implementation (#11757)</title>
<updated>2020-06-30T17:40:18+00:00</updated>
<author>
<name>nicole mazzuca</name>
<email>mazzucan@outlook.com</email>
</author>
<published>2020-06-30T17:40:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/vcpkg/commit/?id=1d8f0acc9c3085d18152a3f639077a28109196b6'/>
<id>1d8f0acc9c3085d18152a3f639077a28109196b6</id>
<content type='text'>
==== 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"` -&gt; `"maintainers"`
  * `--x-classic-mode` -&gt; `-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
  * `&lt;license-string&gt;`: SPDX v3.8 -&gt; v3.9
  * `"feature"."description"` is allowed to be an array of strings as well
  * `"version"` -&gt; `"version-string"` for forward-compat with versions
    RFC
* Add the `--feature-flags` option
* Add the ability to turn off feature flags via passing
  `-&lt;feature-flag&gt;` 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: &lt;my-version&gt;-&lt;port-version&gt;`

==== Smaller changes ====
* small drive-by cleanups to some CMake
  * `${_VCPKG_INSTALLED_DIR}/${VCPKG_TARGET_TRIPLET}` -&gt;
    `${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&lt;` and friends to `StringView`
* Add `substr` to `StringView`
* SourceParagraphParser gets some new errors</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
==== 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"` -&gt; `"maintainers"`
  * `--x-classic-mode` -&gt; `-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
  * `&lt;license-string&gt;`: SPDX v3.8 -&gt; v3.9
  * `"feature"."description"` is allowed to be an array of strings as well
  * `"version"` -&gt; `"version-string"` for forward-compat with versions
    RFC
* Add the `--feature-flags` option
* Add the ability to turn off feature flags via passing
  `-&lt;feature-flag&gt;` 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: &lt;my-version&gt;-&lt;port-version&gt;`

==== Smaller changes ====
* small drive-by cleanups to some CMake
  * `${_VCPKG_INSTALLED_DIR}/${VCPKG_TARGET_TRIPLET}` -&gt;
    `${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&lt;` and friends to `StringView`
* Add `substr` to `StringView`
* SourceParagraphParser gets some new errors</pre>
</div>
</content>
</entry>
<entry>
<title>[avisynthplus] Upgrade to 3.6.0 (#11736)</title>
<updated>2020-06-11T01:04:32+00:00</updated>
<author>
<name>wangqr</name>
<email>wangqr@users.noreply.github.com</email>
</author>
<published>2020-06-11T01:04:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/vcpkg/commit/?id=1509b14bb3e100ff579bc42c5923ed2871467844'/>
<id>1509b14bb3e100ff579bc42c5923ed2871467844</id>
<content type='text'>
* [avisynthplus] Upgrade to 3.6.0

AviSynth+ also supports linux and macOS now

* [avisynthplus] Allow x64-linux build fail on CI

AviSynth+ requires C++17 to build correctly. C++17 std::filesystem is not available in gcc 7.5 used in CI.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* [avisynthplus] Upgrade to 3.6.0

AviSynth+ also supports linux and macOS now

* [avisynthplus] Allow x64-linux build fail on CI

AviSynth+ requires C++17 to build correctly. C++17 std::filesystem is not available in gcc 7.5 used in CI.</pre>
</div>
</content>
</entry>
<entry>
<title>[avisynthplus] Add new port (#10496)</title>
<updated>2020-04-16T20:44:18+00:00</updated>
<author>
<name>wangqr</name>
<email>wangqr@users.noreply.github.com</email>
</author>
<published>2020-04-16T20:44:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/vcpkg/commit/?id=b7ef16861f37a4a2f1e8ea12137b1349133ee5cf'/>
<id>b7ef16861f37a4a2f1e8ea12137b1349133ee5cf</id>
<content type='text'>
* [avisynthplus] Add new port

* [avisynthplus] Disable static build

Static build is not supported. See https://github.com/AviSynth/AviSynthPlus/issues/130

* [avisynthplus] Ass Supports to CONTROL

* [avisynthplus] set static to fail in CI baseline

* [avisynthplus] add vcpkg_fail_port_install</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* [avisynthplus] Add new port

* [avisynthplus] Disable static build

Static build is not supported. See https://github.com/AviSynth/AviSynthPlus/issues/130

* [avisynthplus] Ass Supports to CONTROL

* [avisynthplus] set static to fail in CI baseline

* [avisynthplus] add vcpkg_fail_port_install</pre>
</div>
</content>
</entry>
</feed>
