Revert cmake version for linux_arm64 #129
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When compiling duckdb-spatial with the latest extension-ci-tools, linux_arm64 have started failing. Upon further investigation it seems like upgrading the CMake version is the culprit. Specifically, CMake 3.21 is ok, but >= 3.25 breaks.
duckdb-spatial is a bit different than other extension builds in that it doesn't entirely rely on Vcpkg for dependencies but also builds some dependencies using the "recursive cmake" technique. My guess is that something changed in cmake that affected how variables are passed down/interpreted from/to subprocesses which causes the cross-compilation toolchain to be misconfigured for the nested cmake projects, causing them to compile with the host toolchain, which eventually leads to linking errors.
We should eventually move the rest of spatial to use only vcpkg (I tried, but GDAL doesn't build out-of-the box on the community triplets such as mingw64/wasm) and/or bisect this further, but for now the simplest solution is to downgrade the CMake version we use for this arch.