OK, the gendef steps makes sense. But...
An issue is that C++ files, when compiled with Visual Studio 2017, show both vcruntime140.dll and msvcp140.dll as dependencies (along with a bunch of api-ms*.dll files). On the other hand, C only executables show just vcruntime140.dll and the api-ms*.dll files. So, the question remains, do I only do vcruntime140.dll, or do I take care of msvcp140.dll (and perhaps msvcr140.dll)? For the latter, I haven't been able to get an executable I built to depend on msvcr140.dll, so I don't know if that no longer matters. Thanks, Tom -----Original Message----- From: Liu Hao <[email protected]> Sent: Saturday, March 23, 2019 10:01 AM To: [email protected]; Biswapriyo Nath <[email protected]> Subject: Re: [Mingw-w64-public] Adding Visual Studio 2017 support to MinGW-w64 在 2019/3/23 20:56, Biswapriyo Nath 写道: > There should be a proper contribution guide in this repository. Like > what to do, what not to do, how to do etc. > > There is some documentation at <https://sourceforge.net/p/mingw-w64/wiki2/Home/>. It is sort of incomplete, though. >From what I have learned from most open source projects, when people are in >doubt, copying-and-pasting would always be an approach. Particularly about >this MSVCR*.DLL thing, copying existent code for MSVCR120.DLL with a few >modifications would probably resolve it. Well, essentially, humans are >repeaters. :| -- Best regards, LH_Mouse _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
