Re: [Gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-10-02 Thread Tamas Szekeres
2009/10/2 iotc : > > For now I think we'd better label our x64 build very experimental. > I think you don't require to mark the whole stuff as experimental just because of the ECW driver itself. I guess you'll probably compile ECW as a plugin and deploy those files separately and mark that package

Re: [Gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-10-02 Thread iotc
Mateusz and Tamas - I've got it working now too, thanks to your help, and the suggested posts clarify a lot of issues. I also had a quick look at these articles at http://extended64.com/forums/p//98187.aspx . It was quite sobering - libecwjp2 and our own ocx seems littered with x64-porting pi

Re: [Gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-10-01 Thread Tamas Szekeres
Hi Paul, I'm using pretty much the same preproc definitions WIN64;WIN32;NDEBUG;_WINDOWS;_USRDLL;UNICODE;_MBCS;LIBECWJ2;QT_DLL;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE However I'm not sure exactly what else have been done in order to get it to run smoothly. As far as I remember we've got

Re: [Gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-10-01 Thread Paul Meems
Tamas, Mateusz and Rob, Thanks for all your help. It seems I can now successfully build to 64Bit. In my first attempt I replaced Win32 with Win64 in the Preprocessor Definitions. That gave me the "unknown machine type will require custom 64 bit variables" error. When I restored Win32 I got the __a

Re: [Gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-10-01 Thread iotc
Hi Tamas and Mateusz Your time on helping us much appreciated. I am working with Paul in the MapWindow team and I implemented the macro fix to libecwj2 a few months ago (by strange coincidence I also chose NCS_ as the prefix). libecwj2.dll compiles fine in VS2008 in WIN32, but we are experiencin

Re: [gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-10-01 Thread Tamas Szekeres
2009/10/1 Mateusz Loskot : > > A side note, I'm not sure it's legal to publish this source code. > I don't intend to publish that, just for tracking this issue down, it will be removed soon. Best regards, Tamas ___ gdal-dev mailing list gdal-dev@lists

Re: [gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-10-01 Thread Mateusz Loskot
Tamas Szekeres wrote: > Mateusz, > > I don't remember if I had to patch ecw this way to compile on Win64. The problem does not seem to be related to 32 vs 64-bit. It is related to scope-less Windows API macros as identified here: http://lists.osgeo.org/pipermail/gdal-dev/2009-July/021393.html A

Re: [gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-10-01 Thread Tamas Szekeres
Mateusz, I don't remember if I had to patch ecw this way to compile on Win64. I've uploaded the package I'm using which compiles well with VS2008 http://vbkto.dyndns.org/tests/libecwj2-3.3-VC9.rar Just open the solution file in Source\NCSBuildQmake and rebuild. You could diff it to your version

Re: [gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-10-01 Thread Mateusz Loskot
Mateusz Loskot wrote: > Paul Meems wrote: >> GDAL is compiling great, except when using libecwj2.dll. Because I can >> 't compile the libecwj2 library for Win-64Bit. >> In some of the header files is stated when compiling to a 64-Bit >> version raise an error. > > What errors? > > It's said to sa

Re: [gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-09-30 Thread Tamas Szekeres
Paul, You can download any of the -dev packages containing the required libs to compile against libecw at this location: http://vbkto.dyndns.org/sdk/ Best regards, Tamas 2009/9/30 Paul Meems : > Hi all, > > We're using GDAL and libecwj2.dll in our application: MapWindow GIS > (www.mapwindow.

Re: [gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-09-30 Thread Mateusz Loskot
Paul Meems wrote: Mateusz, I'll get the compiler and compilation procedure (command, flags) tonight and if needed I'll send them to the list. I can set WIN32 but don't I need WIN64? No, you don't as it's always defined: Windows 32-bit: WIN32 Windows 64-bit: WIN32 && WIN64 Best regards, --

Re: [gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-09-30 Thread Mateusz Loskot
Paul Meems wrote: Mateusz, I'm getting error in NCSTypes.h #error : unknown machine type will require custom 64 bit variables It looks like there may be something misconfigured, build configuration, and "#ifdef WIN32" is not being caught (WIN32 not defined), so it skips to unknown platform cl

Re: [gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-09-30 Thread Mateusz Loskot
Paul Meems wrote: GDAL is compiling great, except when using libecwj2.dll. Because I can 't compile the libecwj2 library for Win-64Bit. In some of the header files is stated when compiling to a 64-Bit version raise an error. What errors? It's said to say, but code of libecwj is well-known [1]

[gdal-dev] Looking for libecwj2.dll Win-64Bit version

2009-09-30 Thread Paul Meems
Hi all, We're using GDAL and libecwj2.dll in our application: MapWindow GIS ( www.mapwindow.org) I'm trying to compile a Win-64Bit version of MapWindow. To do that I need to compile all supporting libraries to Win-64Bit version as well. GDAL is compiling great, except when using libecwj2.dll. Beca