ci(NODE-7409): Use CMake's builtin control for the MSVCRT link mode on libmongocrypt#122
Conversation
libmongocrypt provided a configuration parameter to control the type of the MSVC runtime library. This parameter was redundant with the control that is offered by CMake already. Prefer instead to use that control. The parameter, CMAKE_MSVC_RUNTIME_LIBRARY, was added in CMake 3.15, which is the minimum CMake version required by libmongocrypt.
|
@vector-of-bool Looks like windows builds are failing |
|
The issue appears to be that it's spawning the subprocesss with I can't see in the commit history why I've removed the |
|
@vector-of-bool We don't actually know, this is just something we've used in the past to make our tooling work. But that doesn't mean our scripts can't be made to work without it. Have you tried escaping the angle brackets? |
|
Angle bracket escaping should be unnecessary if the command is not being interpreted by a shell, so I really don't know why it fails now. Regardless, the angle bracket magic is not totally necessary and we can just pass |
|
For reference: The |
Corrected the comment formatting for clarity.
e353c15
Description
Summary of Changes
libmongocrypt provided a configuration parameter to control the type of the MSVC runtime library. This parameter was redundant with the control that is offered by CMake already. Prefer instead to use that control.
The parameter,
CMAKE_MSVC_RUNTIME_LIBRARY, was added in CMake 3.15, which is the minimum CMake version required by libmongocrypt.What is the motivation for this change?
We are trying to simplify libmongocrypt's build, which includes removing redundancy with built-in CMake functionality. This specifically is related to MONGOCRYPT-876, which seeks to remove the
ENABLE_WINDOWS_STATIC_RUNTIMEconfiguration parameter.Double check the following
npm run check:lint)type(NODE-xxxx)[!]: descriptionfeat(NODE-1234)!: rewriting everything in coffeescript