Re: [gdal-dev] Re: GDAL 1.7.2 Windows compilation JAVA JNI doesn't work SOLVED

2010-08-06 Thread Zdeněk Vráblík
osgeo.org > Subject: RE: [gdal-dev] Re: GDAL 1.7.2 Windows compilation JAVA JNI doesn't > work > > Looks like your path may have another version of libexpat somewhere probably > x86. I usually see these kind of errors when accidentally mix-n-match 32 and > 64 bit dlls. Basical

RE: [gdal-dev] Re: GDAL 1.7.2 Windows compilation JAVA JNI doesn't work

2010-08-06 Thread Harsh Govind
g] On Behalf Of Harsh Govind Sent: Friday, August 06, 2010 9:17 AM To: gdal-dev@lists.osgeo.org Subject: RE: [gdal-dev] Re: GDAL 1.7.2 Windows compilation JAVA JNI doesn't work Looks like your path may have another version of libexpat somewhere probably x86. I usually see these kind of e

RE: [gdal-dev] Re: GDAL 1.7.2 Windows compilation JAVA JNI doesn't work

2010-08-06 Thread Harsh Govind
Looks like your path may have another version of libexpat somewhere probably x86. I usually see these kind of errors when accidentally mix-n-match 32 and 64 bit dlls. Basically a 64 bit native application is trying to instantiate a 32 bit application. Regards, Harsh Govind -Original Messa

Re: [gdal-dev] Re: GDAL 1.7.2 Windows compilation JAVA JNI doesn't work

2010-08-05 Thread Tamas Szekeres
Hi, Switcing to x64 should produce x64 compatible libs and dll with the expat solution. You can use de Depends tool to inspect libexpat.dll whether it's an x64 or x32 image. BTW: If you don't want to make your hands dirty with the compilation just download one of the SDK packages from http://vbkto