From 6f2e2c8e3c78554155e9488174317240b34d668d Mon Sep 17 00:00:00 2001 From: Chocobo1 Date: Sun, 22 May 2022 13:14:26 +0800 Subject: [PATCH] Updated Compilation: Windows (MSVC 2019, 64 bit, static linkage) (markdown) --- Compilation:-Windows-(MSVC-2019,-64-bit,-static-linkage).md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Compilation:-Windows-(MSVC-2019,-64-bit,-static-linkage).md b/Compilation:-Windows-(MSVC-2019,-64-bit,-static-linkage).md index cbaeeb1..e5da5dc 100644 --- a/Compilation:-Windows-(MSVC-2019,-64-bit,-static-linkage).md +++ b/Compilation:-Windows-(MSVC-2019,-64-bit,-static-linkage).md @@ -61,7 +61,7 @@ cd .\vcpkg ### Install the base dependencies ``` -.\vcpkg install boost-circular-buffer:x64-windows-static openssl:x64-windows-static qt5-base:x64-windows-static qt5-svg:x64-windows-static qt5-tools:x64-windows-static qt5-winextras:x64-windows-static +.\vcpkg install boost-circular-buffer:x64-windows-static boost-stacktrace:x64-windows-static openssl:x64-windows-static qt5-base:x64-windows-static qt5-svg:x64-windows-static qt5-tools:x64-windows-static qt5-winextras:x64-windows-static ``` Note that by default, `vcpkg` keeps all the buildtrees after each package installation. This is useful for patching and rebuilding, but they can take up a lot of space, so if you don't need them, you can additionally pass the `--clean-after-build` flag to the above command so that the buildtrees are deleted automatically after the installation. Or just delete them manually after the build is done.