Tamas, Mateusz and Rob,<br><br>Thanks for all your help.<br>It seems I can now successfully build to 64Bit.<br>In my first attempt I replaced Win32 with Win64 in the Preprocessor Definitions.<br>That gave me the "unknown machine type will require custom 64 bit variables" error.<br>
When I restored Win32 I got the __asm keyword (Inline Assembler) error Rob is talking about.<br>Now I added Win64 to the Preprocessor Definitions, so having both Win32 and Win64 and it compiles OK.<br>My Preprocessor Definitions for Release|x64 is now:<br>
QT_NO_DEBUG;NDEBUG;_WINDOWS;UNICODE;WIN32;WIN64;_MBCS;_UNICODE;LIBECWJ2;QT_DLL<br>I can't say I understand, but that's is my lack of understanding C++ ;) but it works.<br>I haven't checked if it is a true 64Bit dll, because I don't know how to ;)<br>
<br>I'll now try and compile GDAL to 64Bit with this dll.<br><br>--<br>Paul<br><br><br><div class="gmail_quote">2009/10/1 iotc <span dir="ltr"><<a href="mailto:iotc2000@gmail.com">iotc2000@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Hi Tamas and Mateusz<br>
<br>
Your time on helping us much appreciated. I am working with Paul in the<br>
MapWindow team and I implemented the macro fix to libecwj2 a few months ago<br>
(by strange coincidence I also chose NCS_ as the prefix).<br>
<br>
libecwj2.dll compiles fine in VS2008 in WIN32, but we are experiencing<br>
difficulties in making a x64 build. The main problem is that one of the key<br>
developers in MapWindow has moved on and the rest of us are not very clued<br>
up in C++.<br>
<br>
The error that Paul refers to occurs in lcms.h ("Little cms") in a call to<br>
the __asm keyword (Inline Assembler). I think that that could be fixed quite<br>
easily. However, we simply don't know what other changes need to be made to<br>
libecwj2 for a safe x64 build.<br>
<br>
Tamas - would it be possible to post that library again for a short time? -<br>
did you make #ifdef(WIN32) changes anywhere, and are there any special<br>
compilation flags that we need to change in VS2008?<br>
<br>
Best Regards<br>
Rob<br>
<br>
P.S. When I contacted Mark Sheridan of ERDAS in June about the legality of<br>
my changes, he hinted that development on the libecwj2 SDK is continuing but<br>
it would not be available as before. He wrote:<br>
"The older public 3.3 SDK is known to build with VS 2005, not sure about<br>
2008, as we never ported that version internally. We do have a much newer<br>
version available to licensees with support for VS 2005/2008 in 32 and 64<br>
bit, as well as other enhancements like improved caching, GML in JP2 support<br>
and JP2 opacity channels"<br>
<font color="#888888">--<br>
View this message in context: <a href="http://n2.nabble.com/Looking-for-libecwj2-dll-Win-64Bit-version-tp3741096p3750840.html" target="_blank">http://n2.nabble.com/Looking-for-libecwj2-dll-Win-64Bit-version-tp3741096p3750840.html</a><br>
Sent from the GDAL - Dev mailing list archive at Nabble.com.<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
</div></div></blockquote></div><br>