Opened 8 years ago
Closed 8 years ago
#6501 closed defect (fixed)
PROJSO variable mingw creates libproj-9.dll
| Reported by: | rashadkm | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.2.0 |
| Component: | default | Version: | svn-trunk |
| Severity: | normal | Keywords: | |
| Cc: |
Description
when cross building gdal with proj for mingw. I have dll for libproj but there is crash because of dll name check done in GDAL.
one of my colleague pointed out that gdal checks for only libproj-0.dll during runtime (gdal/ogr/ogrct.cpp)
So either I must use PROJSO or create libproj-0.dll. Maintaining env var everywhere seems a bad idea.
Is there anyway GDAL could pickup correct dll name during configure for windows platform? wheather it be libproj-0 or libproj-9
https://trac.osgeo.org/gdal/browser/branches/2.1/gdal/ogr/ogrct.cpp#L86
Change History (1)
comment:1 by , 8 years ago
| Milestone: | → 2.2.0 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
With the dlopen() mechanism it is hard to guess the right shared object name. A better solution might be to ./configure --with-static-proj4=.... instead to have a linking done at build time (contrary to what the name of the switch might suggest, it actually can link against the shared library)
trunk r34206 "OGRCT: upgrade LIBNAME of mingw and cygwin to libproj-9.dll and cygproj-9.dll to be uptodate with proj 4.9.X (recommended method is using ./configure --with-static-proj4 instead) (#6501)"