<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vcpkg/scripts/e2e_ports/overlays, 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] Download vcpkg.exe rather than building it in bootstrap on Windows. (#15474)</title>
<updated>2021-02-04T18:15:44+00:00</updated>
<author>
<name>Billy O'Neal</name>
<email>bion@microsoft.com</email>
</author>
<published>2021-02-04T18:15:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/vcpkg/commit/?id=aa60b7efa56a83ead743718941d8b320ef4a05af'/>
<id>aa60b7efa56a83ead743718941d8b320ef4a05af</id>
<content type='text'>
This reduces bootstrap cost for Windows customers, resolving the issue initially submitted as #12502 .

The `toolsrc` tree was extracted to https://github.com/microsoft/vcpkg-tool. `bootstrap.sh` was changed to download the right source tarball, extract, and build it. This was chosen over the previous attempt, a submodule, over concerns of accidentally destroying people's local modifications.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reduces bootstrap cost for Windows customers, resolving the issue initially submitted as #12502 .

The `toolsrc` tree was extracted to https://github.com/microsoft/vcpkg-tool. `bootstrap.sh` was changed to download the right source tarball, extract, and build it. This was chosen over the previous attempt, a submodule, over concerns of accidentally destroying people's local modifications.
</pre>
</div>
</content>
</entry>
<entry>
<title>[vcpkg] Add vcpkg_minimum_required as a replacement for VERSION.txt. (#15638)</title>
<updated>2021-01-20T20:07:41+00:00</updated>
<author>
<name>Billy O'Neal</name>
<email>bion@microsoft.com</email>
</author>
<published>2021-01-20T20:07:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/vcpkg/commit/?id=4d136ef25f4fab5b744c7ae6acfa04d44f254f2b'/>
<id>4d136ef25f4fab5b744c7ae6acfa04d44f254f2b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[vcpkg registries] support versions (#15114)</title>
<updated>2020-12-21T23:40:21+00:00</updated>
<author>
<name>nicole mazzuca</name>
<email>mazzucan@outlook.com</email>
</author>
<published>2020-12-21T23:40:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/vcpkg/commit/?id=c898283a41af23135c048c50836f2bc2eccea819'/>
<id>c898283a41af23135c048c50836f2bc2eccea819</id>
<content type='text'>
* [vcpkg registries] support versions

This PR merges the Registries changes and the versioning changes, so that one can use both at the same time.

There is one major difference between this PR and the RFC (#13590), which is that instead of version files looking like:

```json
[
  ...
]
```

version files look like:

```
{
  "versions": [
    ...
  ]
}
```

this is to support interop between this PR and existing demos and the like;
fixing this, along with perhaps renaming `port_versions` to `port-versions` should be done after this is merged,
should be a trivial change.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* [vcpkg registries] support versions

This PR merges the Registries changes and the versioning changes, so that one can use both at the same time.

There is one major difference between this PR and the RFC (#13590), which is that instead of version files looking like:

```json
[
  ...
]
```

version files look like:

```
{
  "versions": [
    ...
  ]
}
```

this is to support interop between this PR and existing demos and the like;
fixing this, along with perhaps renaming `port_versions` to `port-versions` should be done after this is merged,
should be a trivial change.</pre>
</div>
</content>
</entry>
</feed>
