First off, congratulations for getting the mingw compilers off the ground, @isuruf!
In the notes for today's core call, you note:
MinGW UCRT compilers are ready to test
gcc and VC are compatible (C only), but gxx is not (different C++ libraries)
R and Python use different C++ libraries, so we need to be careful about directly linking across this ecosystem boundary.
I was wondering if there's a fundamental blocker for aligning this with our platform defaults, and thus avoid this boundary in the first place? After all, for clangxx_win-64, we manage to use the windows C++ libraries as well.
We might even be able to reuse msvc-headers-libs / winsdk directly? I'm assuming that R doesn't actually depend on a specific flavour of C++ stdlib (I'd be surprised if it did...).
First off, congratulations for getting the mingw compilers off the ground, @isuruf!
In the notes for today's core call, you note:
I was wondering if there's a fundamental blocker for aligning this with our platform defaults, and thus avoid this boundary in the first place? After all, for
clangxx_win-64
, we manage to use the windows C++ libraries as well.We might even be able to reuse
msvc-headers-libs
/winsdk
directly? I'm assuming that R doesn't actually depend on a specific flavour of C++ stdlib (I'd be surprised if it did...).