<!DOCTYPE html><html><head>
<style type="text/css">body { font-family:'Times New Roman'; font-size:13px}</style>
</head>
<body><div>Kurt,</div><div><br></div><div>The Tamas SDKs are not enough as to provide all the dependencies to a GDAL Win installation. It miss all those dlls (didn't check if the list is complete) that the VS2015/17 builds now depend on. So if one wants to distribute a program that depends on GDAL (GMT, in y case) that long list of dlls must be supplied as well or otherwise tell users that they have to install a MS distributable package.</div><div><br></div><div>
Not a killer feature but annoying certainly.
</div><div><br></div><div>Yes, if one remains at GDAL <= 2.2 this issue does not exist.</div><div>I'm not building GDAL against GEOS so didn't know about it C++11 requirement.</div><div><br></div><div>Side and non relevant info, 3 weeks ago I was at the Southern Hemisphere.</div><div><br></div><div><br></div><div>Joaquim</div><div><br></div><div>api-ms-win-core-console-l1-1-0.dll<br>api-ms-win-core-datetime-l1-1-0.dll<br>api-ms-win-core-debug-l1-1-0.dll<br>api-ms-win-core-errorhandling-l1-1-0.dll<br>api-ms-win-core-file-l1-1-0.dll<br>api-ms-win-core-file-l1-2-0.dll<br>api-ms-win-core-file-l2-1-0.dll<br>api-ms-win-core-handle-l1-1-0.dll<br>api-ms-win-core-heap-l1-1-0.dll<br>api-ms-win-core-interlocked-l1-1-0.dll<br>api-ms-win-core-libraryloader-l1-1-0.dll<br>api-ms-win-core-localization-l1-2-0.dll<br>api-ms-win-core-memory-l1-1-0.dll<br>api-ms-win-core-namedpipe-l1-1-0.dll<br>api-ms-win-core-processenvironment-l1-1-0.dll<br>api-ms-win-core-processthreads-l1-1-0.dll<br>api-ms-win-core-processthreads-l1-1-1.dll<br>api-ms-win-core-profile-l1-1-0.dll<br>api-ms-win-core-rtlsupport-l1-1-0.dll<br>api-ms-win-core-string-l1-1-0.dll<br>api-ms-win-core-synch-l1-1-0.dll<br>api-ms-win-core-synch-l1-2-0.dll<br>api-ms-win-core-sysinfo-l1-1-0.dll<br>api-ms-win-core-timezone-l1-1-0.dll<br>api-ms-win-core-util-l1-1-0.dll<br>api-ms-win-crt-conio-l1-1-0.dll<br>api-ms-win-crt-convert-l1-1-0.dll<br>api-ms-win-crt-environment-l1-1-0.dll<br>api-ms-win-crt-filesystem-l1-1-0.dll<br>api-ms-win-crt-heap-l1-1-0.dll<br>api-ms-win-crt-locale-l1-1-0.dll<br>api-ms-win-crt-math-l1-1-0.dll<br>api-ms-win-crt-multibyte-l1-1-0.dll<br>api-ms-win-crt-private-l1-1-0.dll<br>api-ms-win-crt-process-l1-1-0.dll<br>api-ms-win-crt-runtime-l1-1-0.dll<br>api-ms-win-crt-stdio-l1-1-0.dll<br>api-ms-win-crt-string-l1-1-0.dll<br>api-ms-win-crt-time-l1-1-0.dll<br>api-ms-win-crt-utility-l1-1-0.dll</div><div><br></div><div><br></div><blockquote style="margin: 0 0 0.80ex; border-left: #0000FF 2px solid; padding-left: 1ex"><div dir="ltr"><div>Joaquim,<br></div><div><br></div><div>Please give it another go at explaining what this use case is and the issues with it. I didn't follow your comments about the need for VS2013. If users are on a legacy compiler (w.r.t. to C++11), can they not be served by the 2.2 branch? How does that use case fair with the impending GEOS 3.7.0 requiring a minimum of C++11?</div><div><br></div><div>Thanks,</div><div>-kurt</div><div><br></div><div>P.S. Doesn't really matter, but here is where I upped the version for VS on Aug 14 after some discussion with Even:</div><div><br></div><div><a href="https://trac.osgeo.org/gdal/wiki/rfc68_cplusplus11?action=diff&version=9&old_version=8">https://trac.osgeo.org/gdal/wiki/rfc68_cplusplus11?action=diff&version=9&old_version=8</a></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 6, 2017 at 11:23 AM, Mateusz Loskot <span dir="ltr"><<a href="mailto:mateusz@loskot.net" target="_blank">mateusz@loskot.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 6 September 2017 at 20:18, Joaquim Luis <<a href="mailto:jluis@ualg.pt">jluis@ualg.pt</a>> wrote:<br>
> On Wed, 06 Sep 2017 18:34:06 +0100, Mateusz Loskot <<a href="mailto:mateusz@loskot.net">mateusz@loskot.net</a>> wrote:<br>
>> On 6 September 2017 at 19:14, Joaquim Luis <<a href="mailto:jluis@ualg.pt">jluis@ualg.pt</a>> wrote:<br>
>>><br>
>>> Wait, does this means that VS2013 will no longer be supported?<br>
>><br>
>> With respect, Kurt has been asking for comments for very long time.<br>
><br>
</span><span class="">> Yes that's true, but always understood that VS2013 would be the minimum.<br>
<br>
</span>Kurt posted [1] updated RFC 68 three weeks ago.<br>
It would be enough to have a glance to see VS2015.<br>
<br>
[1] <a href="https://lists.osgeo.org/pipermail/gdal-dev/2017-August/046951.html" rel="noreferrer" target="_blank">https://lists.osgeo.org/pipermail/gdal-dev/2017-August/046951.html</a><br>
<div class="HOEnZb"><div class="h5"><br>
Best regards,<br>
--<br>
Mateusz Loskot, <a href="http://mateusz.loskot.net" rel="noreferrer" target="_blank">http://mateusz.loskot.net</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">--<div><a href="http://schwehr.org" target="_blank">http://schwehr.org</a></div></div>
</div>
</blockquote><br><br><br></body></html>