what does "building static library" mean when installing gRPC?

[Stéphane Charette]

(Windows 10, Visual Studio 2019.)

When installing gRPC via vcpkg.exe, I see the following message:

vcpkg.exe install grpc:x64-windows

...

Starting package 6/6: grpc:x64-windows

Building package grpc[core]:x64-windows...

-- Note: grpc only supports static library linkage. Building static library.

Does this mean that gRPC is always built with the static /MT flag?  If not, what exactly does this message mean so I can have a better understanding of the implications.

I'm seeing segfaults and memory corruption in my app as soon as I try to make gRPC calls, so I'm chasing down a bunch of ideas.  The other libs and the rest of the application is built with /MD, so I cannot link to a library built with /MT.

Stéphane Charette

[Jan Tattermusch]

The link for filing grpc vckpkg issues is here: https://github.com/grpc/grpc/tree/master/src/cpp#install-using-vcpkg-package

Build options for the vcpkg package are here: https://github.com/microsoft/vcpkg/blob/a528ee4b856d0d73b6b837dfa7ab2e745d02b5ca/ports/grpc/portfile.cmake#L59