[gdal-dev] Re: gisinternals GDAL builds

[Tamas Szekeres]

Hi Elijah,

With regards to the CRT dependency I would always recommend to use that
version which corresponds to the CRT dep. of the application. You might use
the Dependency Walker tool to identify which CRT dll the application depends
on. For example the official python (python.org) windows builds (python.exe)
use the following dependencies:

Python 2.5 MSVC71 (1310)
Pyrton 2.6 MSVC90 (1500)
Python 2.7 MSVC90 (1500)
Python 3.1 MSVC90 (1500)

Best regards,

Tamas




2011/6/13 Elijah Robison <elijah at villagis.com>

>  Hi Tamas and GDAL devs,
>
> I recently used Tamas' Win binaries (http://www.gisinternals.com/sdk/) to
> install Gdal 1.8 for Python 2.7, and everything is working fine---*Tamas,
> thanks so much for providing those*.
>
> However, I do have a question about selecting the correct release, and want
> to confirm if I "got lucky" on my first shot, or if there is something more
> I should know were I to pass advice along to others.
>
> Under "Compiler (Platform)", I chose MSVC2010 (Win32), which corresponds to
> release-1600-gdal-1-8-0-mapserver-6-0-0<http://PackageList.aspx?file=release-1600-gdal-1-8-0-mapserver-6-0-0.zip>.
> But I am unclear as to what "CRT dependencies" are, as well as the MSVC
> acronym and the 1600-value prepended to the package name (as opposed to
> 1310, 1400, 1500). Would someone mind summarizing these for me?
>
> The various Win binaries include the same array of MSIs, so matching the
> correct Python version is obvious, as well as the 32/64 split----but, would
> my install have worked if I used a different MSVC/number combo?
>
> Thanks in advance for your time,
>
> Elijah Robison
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/gdal-dev/attachments/20110613/9b41e274/attachment.html