Collinbrown95 commented on PR #49553:
URL: https://github.com/apache/arrow/pull/49553#issuecomment-4229935684
Hi @jonkeane and @thisisnic,
I just had a discussion with @marberts, and we wanted to follow up on a
couple of things.
1. @jonkeane I might have misunderstood your comment in my initial response.
Is your suggestion to build the R Arrow library with `-DARROW_AZURE=ON` with
MSVC and host it outside of CRAN (possibly circumventing the MinGW restriction
discussed earlier in this thread)?
If this is your suggestion, could you kindly share a bit more
information about how this would work?
For some extra context, my current understanding is that there are
low-level C++ ABI compatibility issues between binaries built with MSVC and
binaries built with MinGW, which (I think) implies that an MSVC compiled binary
would not interoperate with the rest of the R ecosystem (which I believe is
built with the MinGW toolchain).
That said, I am by no means an expert in R/Windows internals. I would be
happy to learn more if you know of a way for R packages to interoperate with
MSVC-built binaries without ABI issues.
2. I realize I never responded to your question about a path forward for
fixing upstream issues.
The core issue seems to be an incompatibility between Windows
Implementation Libraries (WIL) and MinGW (this is [the issue that @thisisnic
cited earlier in this thread](https://github.com/microsoft/wil/issues/117)).
Our understanding is that resolving this issue would resolve many of the
downstream issues in building
[`azure-sdk-for-cpp`](https://github.com/Azure/azure-sdk-for-cpp) with MinGW,
which would open the door for a fully functioning build of Arrow on Windows
with Azure support enabled.
The most recent discussion on this topic I could find is [this WIL issue
from 2024](https://github.com/microsoft/wil/pull/467). I can create an issue in
either the WIL/MinGW repositories to flag that this compatibility issue is
still relevant, but I get the impression that the scope/timeline of this work
goes beyond what this PR is trying to achieve.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
