I got my development environment working after a bit of messing around.
I read the error message more closely and read about the dependency solver, and
investigated the clcache package. It turns out that clcache has not been
updated since February 2020. As the error message below clearly indic
Thanks Even and Mike.
Using GDAL master works (I presume due to this PR -
https://github.com/OSGeo/gdal/pull/12635).
Working example:
```
conda create --yes --name gdal-master
conda activate gdal-master
conda install -c gdal-master -c conda-forge gdal-master::gdal
$env:Path = "D:\Tools\li
Mike,
I don't remember the details but there's an issue (or at least used to
be last time I tried) with the conda package libadbc-driver-manager on
Windows.
Le 12/07/2025 à 13:46, Michael Smith via gdal-dev a écrit :
Seth,
Have you tried adding https://anaconda.org/conda-forge/libadbc-drive
Seth,
Have you tried adding https://anaconda.org/conda-forge/libadbc-driver-manager
to your conda build and then adding duckdb.dll?
Mike
--
Michael Smith
RSGIS Center – ERDC CRREL NH
US Army Corps
On 7/12/25, 6:51 AM, "gdal-dev on behalf of Seth G via gdal-dev"
mailto:gdal-dev-boun
Seth,
there has been an enhancement in *master* (not in 3.11) for being able
to load libduckdb when the ADBC driver is built without
libadbc-driver-manager support. So if you're not on master, this is
expected
Even
Le 12/07/2025 à 12:45, Seth G via gdal-dev a écrit :
Hi all,
I'm wondering
Hi,
Without any advanced warning, here's a 3.11.3 whose only difference with
3.11.2 is the following fix for a regression that went in 3.11.1:
PG driver:
* restore string truncation that was broken in 3.11.1
Consult the release notes for the list of issues addressed:
https://github.com/
Hi all,
I'm wondering if anyone has got this working on Windows?
With a test.db the following works fine on a full Linux GDAL Docker image:
docker run -it --name gdal-ubuntu -v D:/Data/GDAL:/data
ghcr.io/osgeo/gdal:ubuntu-full-3.11.0 /bin/bash
ogr2ogr out.gpkg test.db
>From the docs https://gd
