[gdal-dev] The proj.dll mistery

Frank Warmerdam warmerdam at pobox.com
Mon Jun 30 20:31:05 EDT 2008


Joaquim Luis wrote:
> Frank Warmerdam wrote:
>>
>> Joaquim,
>>
>> For better or worse, many years ago I had the bright idea of making 
>> PROJ.DLL
>> (or libproj.so) demand loaded when needed so that it wouldn't be a "hard"
>> dependency of GDAL making it harder for people to get things built.  So
>> it does not show up as a dependency.  This is similar to how plugins are
>> handled.  They also won't show up.
> 
> Frank,
> 
> So what is the purpose of this section in nmake.opt?
> I tried with it uncommented but it made no difference.
> 
> # PROJ.4 stuff
> # Uncomment the following lines to link PROJ.4 library statically. 
> Otherwise
> # it will be linked dynamically during runtime.
> #PROJ_FLAGS = -DPROJ_STATIC
> #PROJ_INCLUDE = -IC:\programs\proj4\proj-4.6.0\bin
> #PROJ_LIBRARY = C:\programs\proj4\proj-4.6.0\bin\proj_i.lib

Joaquim,

This is an alternative to dynamically loading PROJ.4.  You might
find you need to do a clean build with these options uncommented.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo, http://osgeo.org



More information about the gdal-dev mailing list