ELKI is compiled using Gradle (note that many IDEs will work with Gradle builds just fine):
On Linux (and supposedly other Unix-like systems, Windows users can use
To build a single-jar ELKI package, run
The resulting standalone package is output to the main folder.
Alternatively, the folder
addons/bundle/build/libs/lib will contain all individual
.jar files required for ELKI.
To manually run ELKI, you need to build a classpath containing:
- the jars of the ELKI modules you want to use
- the jars of required dependencies
(The jars will specify these dependencies, so keeping them in a
dependency/subfolder is enough.)
- additional jars with e.g. your own modules
The following wrapper for Linux (included as
util/launch-packaged.sh) works well. Much of the logic you see below is directory handling and ordering the jars such that the options in the MiniGUI appear in the desired order.
With this wrapper, you can for example enable assertions and increase the memory available to ELKI via the
$JVM_OPTS variable, or choose a different java JVM via
util/launch-compiled.sh will build a complex classpath that includes the compiled, but not yet packaged code. This may be useful to launch the development version.
You can disable addon modules that you do not need by commenting them in