DASCA
/
DASCA
2
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Improved section about WALA configuration.

This commit is contained in:
Achim D. Brucker 2016-10-09 10:21:57 +01:00
parent af7ad992ce
commit 86b16bd570
1 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -34,9 +34,15 @@ mvn install:install-file -Dfile=apktool_2.0.0.jar -DgroupId=apktool -DartifactId
``` ```
### WALA configuration ### WALA configuration
WALA might needs to know the location of the Java JDK (the current DASCA (and the underlying WALA setup) is tested with Java version 8
setup is tested with JDK version 6 and 8). This is configured in the (and version 6). If DASCA is installed using Java 8, there should be
``wala.properties`` file, e.g. no need for updating the WALA configuration.
If you experience problems or want to optimize the performance (e.g.,
by analyzing the programs based on a different Java version), you
might need to configure the the location of the Java JDK. The JDK used
as part of the static analysis is configured in the `wala.properties`
file, e.g.
``` ```
cd DASCA/ cd DASCA/
@ -46,11 +52,6 @@ Don't forget to adjust the path to the Java JDK accordingly, i.e.,
the `<PATH-TO-JDK>` should point to the directory containing the file the `<PATH-TO-JDK>` should point to the directory containing the file
`rt.lib`. `rt.lib`.
If `java_runtime_dir` is not configured, WALA will use the
JDK-libaries of the JDK used for executing WALA. This should work in
most of the cases, i.e., providing a better "out-of-the-box"
expierence.
### How to Compile ### How to Compile
First resolve the dependencies using maven: First resolve the dependencies using maven:
``` ```