[FWTools] lti_dsdk_dll.dll versions?

[jkenneally at cartenav.com]

Hi Tamas,

Thank you for getting back to me so quickly.  I downloaded the updated gdal binaries from your page for a test.  However, I think we are linking against the fw_tools (2.4.7) version of gdal (along with ogr, etc).  

So, for example, fw_tools provides a gdal_i.lib/gdaL-fw.dll that seems to be used instead of gdal17.dll that comes with the default GDAL package.   It is also using renamed dependencies such as "NCSEcwC_fw.dll", "libtiff_fw.dll", etc.

Can anyone comment on what would be involved with switching away from the fw_tools binaries to use the updated gdal binaries you have pointed me to?   If there is nothing special about the fw_tools binaries I don't mind switching away from the fw_tools modules.

One last silly question...I noticed the binaries your page provides dont come with lib/headers?  I can generate a lib from the dll in VS but I just wanted to make sure I wasnt missing something obvious.

Cheers!

-----Original Message-----
From: "Tamas Szekeres" <szekerest at gmail.com>
Sent: Monday, September 27, 2010 7:16pm
To: jkenneally at cartenav.com
Cc: fwtools at lists.maptools.org
Subject: Re: [FWTools] lti_dsdk_dll.dll versions?

Hi,

The MSVC2008 packages available at [http://vbkto.dyndns.org/sdk/] http://vbkto.dyndns.org/sdk/ are compiled against 7.0.0.2181.

Best regards,

Tamas





2010/9/27  <[mailto:jkenneally at cartenav.com] jkenneally at cartenav.com>
Hello,

We've run into an issue with one of the fw_tools dependencies, namely "lti_dsdk_dll.dll".  Our application uses both the latest Global Mapper SDK, and the latest FW_Tools binaries.  A recent release of Global Mapper (which we require for new functionality it introduces) has updated to use a new version of lti_dsdk_dll.dll that doesnt seem to be backwards compatible with the version used in fw_tools.

If I try to run with the older version (6.0.7.1407) of"lti_dsdk_dll.dll" that fw_tools/GDAL depends on, I am getting the followingerror from (I believe )the new Global Mapper SDK at runtime: "Theprocedure entry point ??4LTIPixel at LizardTech@@QAEAAV01@@Z could not belocated in the dynamic link library lti_dsk_dll.dll"

So I figured just updating to the new lti_dsdk_dll.dll version from the Global Mapper sdkwould satisfy both Global Mapper and fw_tools. However, runningwith the newer version (7.0.0.2181) of lti_dsdk_dll.dll gives thefollowing error (I believe from fw_tools): "The procedure entry point?getHeight at LTIImage@LizardTech@@QBEIXZ" could not be located in thedynamic link library lti_dsk_dll.dll"

Having not worked directly with the Geo DSDK libraries, I'm assumingthe new "lti_dsdk_dll.dll" introduced functions global mapper depends on, whiledropping functions that gdal depends on.  (I've inquired with LizardTech to verify this).

So my question is, if/when we could expect new fw_tools binaries for the windows platform that have been updated to use the latest version of lti_dsdk_dll.dll.  Having Global Mapper and FW_Tools both using the same version would be great!

_______________________________________________
FWTools mailing list
[mailto:FWTools at lists.maptools.org] FWTools at lists.maptools.org
[http://lists.maptools.org/mailman/listinfo/fwtools] http://lists.maptools.org/mailman/listinfo/fwtools
[http://fwtools.maptools.org/] http://fwtools.maptools.org/


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maptools.org/pipermail/fwtools/attachments/20100928/b9fd9c57/attachment-0001.htm