[sleuthkit-developers] TSK 4.1.2 Java bindings - Changes needed for DLLs built with Visual Studio 2013?

[Georger A. <geo...@ya...>]

Hi,

I've built TSK 4.1.2 with Visual Studio 2013. I ran ant to build the Java bindings, and it copied the DLLs - libewf.dll, libtsk_jni.dll, and zlib.dll - into dist\Tsk_DataModel.jar. Just for the record, I had to manually create the crt and crt\win32 folders under bindings\java, otherwise ant would complain and fail to build dist\Tsk_DataModel.jar.

Then I built the Autopsy 3.0.8 sources. I ran `ant build` and all was fine, but when I ran `ant run` I got the following messages at the console:

[exec] SleuthkitJNI: failed to load msvcp100
[exec] SleuthkitJNI: failed to load msvcr100
[exec] SleuthkitJNI: loaded zlib
[exec] SleuthkitJNI: loaded libewf
[exec] SleuthkitJNI: loaded libtsk_jni

I looked inside dist\Tsk_DataModel.jar and noticed that NATIVELIBS\i386\win\ didn't contain msvcp100.dll nor msvcp100.dll, just the 3 DLLs that were built when I compiled TSK 4.1.2.

I then looked at bindings\java\src\org\sleuthkit\datamodel\LibraryUtils.java, and in lines 148 and 149 the function tries to explicitly load msvcr100.dll and msvcp100.dll.


My question is, is this a problem? Shouldn't the build script and the source code refer to the runtime DLLs that were used to compile the Java binding - those would be msvcr120.dll and msvcp120.dll from Visual Studio 2013?

In case it helps, these are the software versions I'm running:

Windows 8.1 Pro x64
Visual Studio 2013 Express 32-bit
JDK 7u25 32-bit
ant 1.9.2
TSK 4.1.2
Libewf 20130416
zlib 1.2.8

Autopsy 3.0.8

Regards,

Georger