Hi gdal-devs,
I have a question, if there is some way to use gdalwarp in a clustering system
(e.g., Sparks) or with GPU to speed up the process? My task involves
re-projection and re-sampling of hundreds of high-resolution images. Any ideas
to make use of Sparks or GPU is welcomed. Thank you.
Si
FYI, this is what I do with my build. Since I want to control the DLL name I’ve
added this lines to src\ lib_proj.cmake
# If a renaming of the proj dll has been set in ConfigUser.cmake
if (WIN32 AND PROJ4_DLL_RENAME)
set_target_properties(${PROJ_CORE_TARGET} PROPERTIES RUNTIME_OUTPUT_NAME
${PR
Hi Even,
Thank you, I've not considered to modify the linking behavior of proj.dll
at this stage, but as far as it solves the problem I'm fine with it.
Best regards,
Tamas
Even Rouault ezt írta (időpont: 2020. jan.
22., Sze, 15:01):
> Hi Tamas,
>
> > However the GDAL build (like for
> > http
How to indicate different location for specific libs for rgdal?
I have libgif.so.4 in a different location.
/usr/bin/ld: warning: libgif.so.4, needed by
/home/helder.almeida/local/gnu/gdal/3.0.3/lib/libgdal.so, not found (try
using -rpath or -rpath-link)
I tried:
PKG_CPPFLAGS="-I/home/helder.alme
Hi Tamas,
> However the GDAL build (like for
> https://github.com/OSGeo/gdal/blob/v2.4.4/gdal/ogr/ogrct.cpp) still using
> the default proj.dll name which cannot be configured in the opt file.
It can. You need to define -DPROJ_STATIC for that. -DPROJ_STATIC is a bit
confusing. It didn't mean a s
Hi,
As far as I see the current cmake builds of proj4/proj6 includes the proj
version number into the dll names like *proj_4_9.dll* for a Windows build.
However the GDAL build (like for
https://github.com/OSGeo/gdal/blob/v2.4.4/gdal/ogr/ogrct.cpp) still using
the default proj.dll name which canno
