File: README.txt

package info (click to toggle)
sleuthkit 4.1.3-3~bpo70%2B1
  • links: PTS, VCS
  • area: main
  • in suites: wheezy-backports
  • size: 36,800 kB
  • sloc: ansic: 147,143; sh: 40,085; cpp: 36,823; java: 6,886; makefile: 1,248; xml: 529; python: 409; perl: 59; sed: 16
file content (50 lines) | stat: -rw-r--r-- 1,519 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
Sleuth Kit Java Bindings

Overview

The core functionality of the Sleuth Kit is in the C/C++ library.
The functionality is made available to Java applications by using
JNI.  The theory is that a SQLite database is created by the C++
library and then it is queried by native Java code. JNI methods
exist to make the database and to read file content (and other raw
data that is too large to fit into the database).

To use the Java bindings, you must have the Sleuth Kit datamodel
JAR file compiled and have compiled the associated dynamic library
from the C/C++ code.

Requirements:
* Java JDK
* Ant


Building the Dynamic Library (for JNI)

The win32 Visual Studio solution has a tsk_jni project that will
build the JNI dll.  To use this project, you will need to have
JDK_HOME environment variable set to the root directory of JDK.

On non-windows environments, it should just build as part of running
./configure and make.   If the needed Java components are not found,
it will not be built. 



Building The Jar File

Build with the default ant target (by running 'ant').  This will
download the required libraries (using ivy) and place the jar file
in the dist folder along with the needed dll and library files.


Using the Jar file and Library

Make sure the Jar file is in your CLASSPATH. The dynamic library
will also need to be available when the program is run.  Typically
that means that it must be in the path.  Refer to the javadocs for 
details on using the API

------------
Brian Carrier
Nov 11, 2011