[Gdal-dev] Looking for libecwj2.dll Win-64Bit version
Tamas Szekeres
szekerest at gmail.com
Thu Oct 1 15:45:28 EDT 2009
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 access violations
with GDAL autotests on Win64 but it has also been fixed (I've probably
added a note on this in my source code 'Modified by Tamas Szekeres' or
something like this)
Currently there's no outstanding issues I have in my mind with this
version and I've already used ECW data in my Win64 applications, but
let me know if you find anything.
The ready to use binaries and libs are also available for testing at
the location mentioned before (http://vbkto.dyndns.org/sdk/)
Best regards,
Tamas
2009/10/1 Paul Meems <bontepaarden at gmail.com>:
> 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 <iotc2000 at 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 at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>
More information about the gdal-dev
mailing list