Unsolved
This post is more than 5 years old
2 Posts
0
3563
January 22nd, 2010 13:00
EMC Centera SDK 3.2 Patch 5 for Windows (32-bit) (Build 705) missing .lib files!
We just downloaded EMC Centera SDK 3.2 Patch 5 for Windows (32-bit) (Build 705).
This patch is missing all 32-bit libs necessary for an application to link! FPLibrary.lib, fpos32.lib, fpparser.lib, pai_module.lib are not in \lib or \lib32. We do see a FPlibrary.lib in \lib64 (which is strange because we downloaded the 32-bit package).
We are attempting to upgrade from SDK 3.1.477 as we were advised that version has reached end-of-life. But this latest version seems to be unusable, unless the nature of the SDK has changed such that the above libs are no longer necessary and we are doing something wrong. We did try linking just to the 64-bit FPlibrary.lib that was in the package but we get many missing reference errors, as expected.
We also note that the samples in the patch contain hard-coded invalid paths to some internal EMC machine, so they were not vetted for general distribution.
Please advise.
Thanks,
Chris Yust
Verint Systems
gstuartemc
2 Intern
•
417 Posts
0
January 22nd, 2010 14:00
The solution and project files are used to internally build and test the samples and should not have been included in the packaging.
However, these are easily modified to build within any directory structure that you may have deployed in locally.
There are no "missing" files in the distribution. Static versions of SDK libraries that are not required by integrating applications ceased to be included in distributions over 5 years ago.
As you have are upgrading an existing integration, I assume that you have a build structure in place for your product and are able to find the directory that you use for the Centera SDK libraries and header files. The relevant files within the distribution can simply be "dropped" into place and you can then proceed to build and test your current application with the new SDK.
cyust
2 Posts
0
January 27th, 2010 08:00
Thanks guys for your quick response.
I have identified the problem -- the HTTPS download feature on the SDK website produces a file named "Centera_SDK_Windows" (no extension) for both the 64-bit and 32-bit versions. I downloaded both out of curiosity and must have overwritten the 32-bit version -- my fault. By contrast the FTP download button produces distinguished names like "Centera_SDK_Windows_2000-5.0-Win32Dev8.zip" and "Centera_SDK_Windows_2000-5.0-Win64Dev8.zip" which are unique and descriptive. I am using FireFox 3.5.7 if it matters.
We are capable of changing the sample include and link directories, and executing a drop-in replacement of the new SDK to our existing build process. Just got thrown off by the apparent lack of 32-bit .lib and incorrect sample paths, then assumed that the download ZIP was in general incomplete.
We now have the right 32-bit ZIP and are compiling correctly, thanks!
-Chris