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 __asm keyword (Inline Assembler) error Rob is talking about. Now I added Win64 to the Preprocessor Definitions, so having both Win32 and Win64 and it compiles OK. My Preprocessor Definitions for Release|x64 is now: QT_NO_DEBUG;NDEBUG;_WINDOWS;UNICODE;WIN32;WIN64;_MBCS;_UNICODE;LIBECWJ2;QT_DLL I can't say I understand, but that's is my lack of understanding C++ ;) but it works. I haven't checked if it is a true 64Bit dll, because I don't know how to ;)
I'll now try and compile GDAL to 64Bit with this dll. -- Paul 2009/10/1 iotc <iotc2...@gmail.com> > > 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 experiencing > difficulties in making a x64 build. The main problem is that one of the key > developers in MapWindow has moved on and the rest of us are not very clued > up in C++. > > The error that Paul refers to occurs in lcms.h ("Little cms") in a call to > the __asm keyword (Inline Assembler). I think that that could be fixed > quite > easily. However, we simply don't know what other changes need to be made to > libecwj2 for a safe x64 build. > > Tamas - would it be possible to post that library again for a short time? - > did you make #ifdef(WIN32) changes anywhere, and are there any special > compilation flags that we need to change in VS2008? > > Best Regards > Rob > > P.S. When I contacted Mark Sheridan of ERDAS in June about the legality of > my changes, he hinted that development on the libecwj2 SDK is continuing > but > it would not be available as before. He wrote: > "The older public 3.3 SDK is known to build with VS 2005, not sure about > 2008, as we never ported that version internally. We do have a much newer > version available to licensees with support for VS 2005/2008 in 32 and 64 > bit, as well as other enhancements like improved caching, GML in JP2 > support > and JP2 opacity channels" > -- > View this message in context: > http://n2.nabble.com/Looking-for-libecwj2-dll-Win-64Bit-version-tp3741096p3750840.html > Sent from the GDAL - Dev mailing list archive at Nabble.com. > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev