Hi Stefan, thanks for the answer. In my case the gdald.dll with the recent date from my last compilation is created directly to build\Debug and not to build\apps\Debug (the date it’s older, but not much older, it’s from this morning (??)). Are you sure that your sense of copy is FROM build\apps\Debug TO build\Debug?
And ogr2ogr.exe is loading the one in apps as you can see looking at this dependencies view (using a simple program called depends.exe). [cid:image001.png@01DA69BD.D2F814E0] Once I copy this gdald.dll FROM “no app” to “app” directory IT WORKS. So, your clue has make it work! So, now my question is “why are there two directories where gdald.dll is?”. Today, you've really helped me out of a tight spot. Thanks a lot! And thanks to the other that read and answered!!! De: Uhrig, Stefan <stefan.uh...@sap.com<mailto:stefan.uh...@sap.com>> Enviado el: dimarts, 27 de febrer de 2024 16:50 Para: gdal-dev@lists.osgeo.org<mailto:gdal-dev@lists.osgeo.org> CC: Abel Pau <a....@creaf.uab.cat<mailto:a....@creaf.uab.cat>> Asunto: RE: [gdal-dev] Some problems after updating Hi Abel, I did a Windows Debug build from scratch using the current GDAL head and the current vcpkg head. I could execute ogr2ogr without a problem, but I had to copy it over from build/apps/Debug to build/Debug where the gdald.dll is located. My guess is that your ogr2ogr is not loading the gdald.dll you built but another gdald.dll, maybe the one that vcpkg built. In the directory in which ogr2ogr.exe is located, execute the following command to find out which gdald.dll is actually loaded by ogr2ogr: where gdald.dll This should point to the gdald you built, but I’d assume that it points to another gdald.dll. Best regards, Stefan
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
