Hacker News Reader

Now I just finished three days of work to remove vcpkg.

Windows + vcpkg + MSVC it works perfectly. Windows + vcpkg + clang it is a knightmare of linking problems.

clang is supposed to have a compatible ABI with MSVC as long as you use link.exe for linking. Is this not the case?

http://blog.llvm.org/2018/03/clang-is-now-used-to-build-chro...

clang, and most likely not the version packaged by Microsoft on Visual Studio, that is the problem right there.

Right, I found a tutorial of someone explaining how to use vcpkg with VSCode+CMake [1] (without the VS2019 IDE) and he mentions the process required a lot of trial and error.

VS2019 otoh, in my experience, just worked out of the box (with the single package I tried ...).

1: https://gamefromscratch.com/vcpkg-cpp-easy-mode-step-by-step...

I didn't encounter any problems with vanilla clang on Windows for building projects (installed with "scoop install llvm"), in fact I was surprised that it worked out of the box, even for code that extensively uses Windows APIs). I suspect that it requires a MSVC toolchain installation, or at least the Windows SDK installed, but since everything "just worked" I didn't dive too deeply into what's actually happening under the hood.

Reply on news.ycombinator.com