Bug #6533

wt port in vcpkg

Added by Max Quatember over 4 years ago. Updated over 4 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:



We're using vcpkg for most of our third party dependencies, also for wt.

When using the portfile of the current vcpkg master at

openssl is enabled with -DENABLE_SSL=ON but wt is built without ssl support.

I have to specify the paths to the ssl libraries with


to make it work... (the same with zlib support in built-in-http)

My environment:

Windows 10, VC 2017

Is this an error in auto-finding ssl/zlib-libraries via cmake in the wt cmake-build?




Updated by Roel Standaert over 4 years ago

Yeah, I've tried the vcpkg-ed version of Wt once, and the Conan version of Bincrafters, and I have noticed that they both don't build entirely correctly with all options.

I'm not sure how much of that is Wt's CMake stuff that needs fixing/modernizing (probably true to some extent) and how much of it is just down to providing the correct flags to CMake.

Finding libraries on Windows generally tends to be less straightforward than finding them on Linux, where you can expect to find them in /usr/lib.

I personally would love to see using Wt with vcpkg or Conan become a smoother experience, but I'd need to find the time to fix that. Fixing builds takes a lot of time because there's a lot of waiting for things to build involved. Any contributions (either to our CMakeLists, to vcpkg, or bincrafters/conan-wt) would be welcome.

If you really want to customize your vcpkg build of Wt, their guideline is to have your own fork of the vcpkg repo. I talked to the devs at CppCon and that's what they told me.


Updated by Max Quatember over 4 years ago

Hi Roel!

Thanks for your time + work!

For me forking and customizing works.

If I have a solution for my problems in future, I will contribute it to whomever it belongs (wt-cmake, vcpkg)!

Best regards!


Also available in: Atom PDF