<br><br><div class="gmail_quote">2011/1/6 Ari Jolma <span dir="ltr"><<a href="mailto:ari.jolma@gmail.com">ari.jolma@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"><div class="im">
<br></div>
By the age I meant that the SDK packages are old releases (from 1310
to 1600 and not trunk for example - do I understand the release
names correctly?)<div class="im"><br>
<br></div></div></blockquote><div><br>Ari,<br><br>Those numbers are MSVC compiler numbers (according to <a href="http://trac.osgeo.org/gdal/browser/trunk/gdal/nmake.opt">http://trac.osgeo.org/gdal/browser/trunk/gdal/nmake.opt</a>) not gdal version numbers.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div text="#000000" bgcolor="#ffffff">CPAN has only sources, thus cpan application which is the standard
to download and install perl modules expects you to have a compiler.<br>
<br>
ActivePerl (in fact ActiveState, the company) maintains a repository
of perl modules in binary versions, from where they can be simply
downloaded and installed with another program. ActivePerl has tools
for developing those binary packages. That's very similar to what
Python has. I think ActiveState maintains its repository by itself -
so if I just make the CPAN module intelligent enough it may end up
there eventually. I think my Geo::Shapelib module was/is there.<br>
<br>
I think it would not make sense to include GDAL into such a binary
perl module package. Thus GDAL would need to be separately
installable - the module installer could probably be made to offer
install it for the user if it existed somewhere.<br>
<br></div></blockquote><div><br>This is also the case with python and the other bindings: the gdal dll-s and dependencies should also be installed somewhere. Assuming we install the gdal-perl modules in a standard location (not sure where it is), do we have a common mechanism in the perl runtime to find the dependent dlls without having to violate system wide settings (like the PATH environment variable)?<br>
</div></div><br>Best regards,<br><br>Tamas<br><br><br><div style="visibility: hidden; left: -5000px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 130%;" id="avg_ls_inline_popup">
</div>