Lukas Burgholzer

We are also facing a similar problem over at https://github.com/cda-tum/mqt-core/pull/706 where we use renovate to keep the `uv` lock file up to date, which would be pretty convenient in principle....

Interesting. I removed the SABI component now. That was a relic from when we were trying to switch to nanobind and it hasn't really caused any issues so far to...

Ah, and I now remembered that we also switched to using Ninja at some point because we try to make use of `ccache` (via https://github.com/Chocobo1/setup-ccache-action) as much as we can...

> Those unresolved import errors typically mean that you're referencing a `libs` directory from an x64 install of Python, not from an ARM64 one (these files are platform specific). `cibuildwheel`...

> This is not cross-compiled, this issue the native runner, right? The cibuildwheel specific part you are referring to (and you added) is for cross-compiling, I believe. Yes, this is...

> > DEBUG - Selecting win-amd64 or win-arm64 due to VSCMD_ARG_TARGET_ARCH > > Haha, interesting. Looks like we rely on the CMake default if nothing is selected, rather than passing...

Good points. Before trying that, I quickly reenabled our other Windows CI runs in the PR to make sure that any change works for all use cases. One strange thing...

> Have you activated all verbosity options? `SKBUILD_BUILD_VERBOSE=1` and `SKBUILD_LOGGING_LEVEL=DEBUG` are the envvar versions. Comparing a working and failing build would be very interesting! I generated the following verbose logs:...

> It's a C define, not a CMake define. It needs to be set on building any file that includes Python.h. Gotcha, thanks! Adapted the code accordingly. I also slightly...

> Assuming this is treated like a `\\?\` prefix, this means the path is allowed to be longer than 256 chars, but it also disables path processing, which might cause...