On 2017-03-02 6:14 AM, Jürgen E. Fischer wrote:
Well, if the third party dependencies (like filegdb - which I happend to start
and stop checking) were available that would already be in place.
Maybe I should just drop it in favor of openfilegdb - that's going to happen if
it's still not availab
On jeudi 2 mars 2017 11:14:07 CET Jürgen E. Fischer wrote:
> Hi Even,
>
> On Thu, 02. Mar 2017 at 10:43:16 +0100, Even Rouault wrote:
> > Probably because the last GDAL built in OSGeo4W was done with MSVC2010,
> > before the recent upgrade to MSVC2015 for QGIS master. I guess the next
> > GDAL bui
Hi Even,
On Thu, 02. Mar 2017 at 10:43:16 +0100, Even Rouault wrote:
> Probably because the last GDAL built in OSGeo4W was done with MSVC2010,
> before the recent upgrade to MSVC2015 for QGIS master. I guess the next GDAL
> builds will be done with MSVC2015 too.
Well, if the third party dependenc
Two great answers in 10 minutes! thanks guys!
On 2 March 2017 at 11:43, Mateusz Loskot wrote:
> On 2 March 2017 at 10:32, Idan Miara wrote:
> > Hi,
> >
> > I'm developing a c++ MSVC (2013 or 2015) program that depends on GDAL.
> > Currently I'm using the C API, and I might use the C++ API in th
On 2 March 2017 at 10:32, Idan Miara wrote:
> Hi,
>
> I'm developing a c++ MSVC (2013 or 2015) program that depends on GDAL.
> Currently I'm using the C API, and I might use the C++ API in the future.
>
> I've run dependency walker on the recent version of gdal201.dll that is
> distributed in osge
On jeudi 2 mars 2017 11:32:11 CET Idan Miara wrote:
> Hi,
>
> I'm developing a c++ MSVC (2013 or 2015) program that depends on GDAL.
> Currently I'm using the C API, and I might use the C++ API in the future.
>
> I've run dependency walker on the recent version of gdal201.dll that is
> distribute
Hi,
I'm developing a c++ MSVC (2013 or 2015) program that depends on GDAL.
Currently I'm using the C API, and I might use the C++ API in the future.
I've run dependency walker on the recent version of gdal201.dll that is
distributed in osgeo4w, it depends on msvcr100.dll, thus I assume it was
com