duckdb
Upgrade dependencies
Note to self:
- Don't build shell on windows as the sqlite symbols conflict
- GDAL requires cpp17 headers that's not available on our CI
GDAL 3.10, GEOS 3.13, and Proj 9.5 are all out now... anything I can help with here?
FYI, there's also a change proposed for both GDAL and PROJ to formalise embedding resources (like proj.db) into the libraries based on your existing approach.
@rcoup Not really, we bumped to latest GEOS separately before DuckDB v1.1.1(I think..). We can't really move forward with latest GDAL because the c++17 requirement is not compatible with our CI setup, and ideally we want spatial to be available on older targets.
By "our CI environment" do you mean https://github.com/duckdb/extension-ci-tools ?
The manylinux2014 toolchain has a newer GCC (v10) from Redhat such that it supports C++17, and there's newer GCC (v9/10/11/13) available from the Ubuntu team for 18.04. So should be possible...
The manylinux2014 toolchain has a newer GCC (v10) from Redhat such that it supports C++17, and there's newer GCC (v9/10/11/13) available from the Ubuntu team for 18.04. So should be possible...
CC @carlopi
Discussed with @Maxxen and @samansmink, I think this is something that would be interesting to look at this in general in the next release cycle.
Extensions (eg. spatial) are free to get ahead and experiment with this, but this comes with some cost, and maybe it's better to do this properly on the tooling side.
