❔ Plans for Windows ARM support 🪟

[adriens]

❔ About

We are currently embedding a duckdb export feature :

• 📤 Add export and duckdb sub-command : geol export duckdb opt-nc/geol#96 (comment)

, and are facing some issues on Gorelaser due to the Windows ARM support which should be available in duckdb v1.4.3.

Do you have some plans on when it will be supported (so we know if we wait or simply adjust the release process on our side)?

[taniabogatsch]

I'd recommend adjusting the release process on your side for now. We're currently close to Go's repository (module) size limit in duckdb-go-bindings, so it is not trivial for us to ship the new binaries there and we are not yet sure how / when we'll address this.

[adriens]

Ok guys thanks a lot for the quick feedback

[mlafeldt]

One blocker for this (at least for static linking) is that DuckDB releases currently only ship static-libs-windows-mingw.zip and nothing ARM-specific yet. Once we have those artifacts in place, we should be able to add Windows ARM support to duckdb-go-binding and then duckdb-go.

[joeblew999]

+1 for this. happy to test !!

[Saramanda9988]

Hi, just following up on this. Has there been any progress on Windows ARM support since the last discussion? It has been about a month, so I was wondering if there are any updates.

[taniabogatsch]

Hi - we've discussed adding Windows ARM to our shipped static libs, but in their current state the GCC-based toolchains on Windows are fragile in general and native stable GCC for Windows ARM is unlikely to exist soon. We likely can do this with cross-compilation, but cannot really guarantee the whole thing (both the build setup and the resulting binaries) to be as robust as for x64.

Based on that, we have decided that shipping Windows ARM with GCC-based toolchain in its current state is not a priority.