because they are already available on windows. We do not need to install any dlls for msvcp.
GCC can link to libc++ too. Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: JonY via Mingw-w64-public <mingw-w64-public@lists.sourceforge.net> Sent: Saturday, May 15, 2021 11:30:45 AM To: mingw-w64-public@lists.sourceforge.net <mingw-w64-public@lists.sourceforge.net> Cc: JonY <jo...@users.sourceforge.net> Subject: Re: [Mingw-w64-public] My new attempt to support msvc stl for mingw-w64 On 5/15/21 2:27 PM, sotrdg sotrdg wrote: > Do you think that is useful? I’ve heard a lot of people they are not happy > with shared linking with libstdc++-6.dll. They want to shared linking with > msvcp. > > some initial attempts · expnkx/MinGW-w64-STL@a2d31c6 > (github.com)<https://github.com/expnkx/MinGW-w64-STL/commit/a2d31c6857d18af61d165aaf56d0aa35ddd6b81b> > some initial attempts · expnkx/MinGW-w64-STL@a2d31c6 > (github.com)<https://github.com/expnkx/MinGW-w64-STL/commit/a2d31c6857d18af61d165aaf56d0aa35ddd6b81b> > Can you explain how this works? Is there a technical reason to use msvcp besides it already available on Windows? If the same msvcp binary is intended to be used, can you also explain how do you plan to overcome compiler ABI and name mangling difference? Is this any different than using libc++ with clang? _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
