aboutsummaryrefslogtreecommitdiff
path: root/build_msvc/vcpkg.json
diff options
context:
space:
mode:
authorAaron Clauson <aaron@sipsorcery.com>2020-09-29 13:48:28 +0100
committerAaron Clauson <aaron@sipsorcery.com>2020-09-29 13:48:28 +0100
commit712f95d3324d02310dd468e7bfd1e1b0df432e77 (patch)
tree3300602820563f8c97bf87e9d2bf01ede25ce358 /build_msvc/vcpkg.json
parent1b313cacc99a1b372238f9036abed5491f9d28f7 (diff)
downloadbitcoin-712f95d3324d02310dd468e7bfd1e1b0df432e77.tar.xz
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.
Diffstat (limited to 'build_msvc/vcpkg.json')
-rw-r--r--build_msvc/vcpkg.json19
1 files changed, 19 insertions, 0 deletions
diff --git a/build_msvc/vcpkg.json b/build_msvc/vcpkg.json
new file mode 100644
index 0000000000..5d5f94227f
--- /dev/null
+++ b/build_msvc/vcpkg.json
@@ -0,0 +1,19 @@
+{
+ "name": "bitcoin-core",
+ "version-string": "1",
+ "dependencies": [
+ "berkeleydb",
+ "boost-filesystem",
+ "boost-multi-index",
+ "boost-process",
+ "boost-signals2",
+ "boost-test",
+ "boost-thread",
+ "double-conversion",
+ {
+ "name": "libevent",
+ "features": ["thread"]
+ },
+ "zeromq"
+ ]
+} \ No newline at end of file