bitcoin/build_msvc/vcpkg.json

{
  "name": "bitcoin-core",
  "version-string": "1",
  "dependencies": [
    "berkeleydb",
    "boost-multi-index",
    "boost-process",
    "boost-signals2",
    "boost-test",
    "sqlite3",
    {
      "name": "libevent",
      "features": ["thread"]
    },
    "zeromq"
  ]
}
Update msvc build to use new vcpkg manifest The vcpkg tool has introduced a proper way to use manifests, https://devblogs.microsoft.com/cppblog/vcpkg-accelerate-your-team-development-environment-with-binary-caching-and-manifests/. This PR replaces the custom text file mechanism with the new manifest approach. It is planned that vckpg manifests will include the ability to version dependencies in the future. Dependency versions would solve a number of issues that currently require workarounds with the appveyor CI. Set vcpkg manifest version to 1 to avoid any perception it's related to any release or other version numbering. 4 years ago			`{`
			`"name": "bitcoin-core",`
			`"version-string": "1",`
			`"dependencies": [`
			`"berkeleydb",`
			`"boost-multi-index",`
			`"boost-process",`
			`"boost-signals2",`
			`"boost-test",`
Add sqlite to travis and depends 5 years ago			`"sqlite3",`
Update msvc build to use new vcpkg manifest The vcpkg tool has introduced a proper way to use manifests, https://devblogs.microsoft.com/cppblog/vcpkg-accelerate-your-team-development-environment-with-binary-caching-and-manifests/. This PR replaces the custom text file mechanism with the new manifest approach. It is planned that vckpg manifests will include the ability to version dependencies in the future. Dependency versions would solve a number of issues that currently require workarounds with the appveyor CI. Set vcpkg manifest version to 1 to avoid any perception it's related to any release or other version numbering. 4 years ago			`{`
			`"name": "libevent",`
			`"features": ["thread"]`
			`},`
			`"zeromq"`
			`]`
Add sqlite to travis and depends 5 years ago			`}`