Note: msvcrt.dll is not a msvc shipped and supported dll, despite its
name. It's a windows implementation detail, essentially. The shipped
and supported msvc dlls are all msvcrt*.dll where * is a version
number, like 80 for 2005.
And the only way to ensure that the dlls are there is to ship them.
Note: msvcrt.dll is not a msvc shipped and supported dll, despite its
name. It’s a windows implementation detail, essentially. The shipped
and supported msvc dlls are all msvcrt*.dll where * is a version
number, like 80 for 2005.
Every MinGW app links to the OS-provided msvcrt.dll by default. It had been like this since the beginning, and it works well. You can explicitly link the numbered versions too, though. Of course it’s ‘supported’ (it’s a core part of the OS) and it’s been shipped with Windows since every version after 98.
The exported API does change from Windows version to Windows version. Libc++ cannot explicitly link to a predefined version, as this would limit the binary’s compatibility.
Ruben
Of course it's 'supported' (it's a core part of the OS) and it's been shipped with Windows since every version after 98.
It exists on those versions of Windows, but it is not supported. But,
it's just advice, I'm sure everyone will do as they will.