Compare commits
5 Commits
bbeb513690
...
72d399bfe1
Author | SHA1 | Date |
---|---|---|
Achim D. Brucker | 72d399bfe1 | |
Achim D. Brucker | 6a11a14b73 | |
Achim D. Brucker | 00242dd2fc | |
Achim D. Brucker | fb1927fcc0 | |
Achim D. Brucker | 4865370393 |
26
README.md
26
README.md
|
@ -11,7 +11,10 @@
|
|||
* JavaScript Development Tools (JSDT)
|
||||
* Gradle Integration (Buildship)
|
||||
* From the [Scala IDE Update Site](http://scala-ide.org/download/current.html)
|
||||
* [Scala IDE and Scalatest Runner (the latter is optional)](http://download.scala-ide.org/sdk/lithium/e44/scala211/stable/site)
|
||||
* [Scala IDE and Scalatest Runner (the latter is optional)](http://download.scala-ide.org/sdk/lithium/e47/scala212/stable/site)
|
||||
If you install the [Eclipse for Java EE Developers](http://www.eclipse.org/downloads/packages/release/2018-09/r/eclipse-ide-java-ee-developers),
|
||||
you should get a version that includes already PDE, JSDT, and Buildship. Thus, you only need
|
||||
to add the Scala IDE.
|
||||
* The native libraries and the JNI packages for [CVC3](http://cs.nyu.edu/acsys/cvc3/).
|
||||
On a Debian-based Linux system, you need to install the package `libcvc3-5-jni`.
|
||||
|
||||
|
@ -30,21 +33,19 @@ DASCA, you can obtain them by executing
|
|||
git submodule update --init --recursive
|
||||
```
|
||||
|
||||
### WALA configuration
|
||||
### Configuration (optional)
|
||||
|
||||
DASCA (and the underlying WALA setup) is tested with Java version 8.
|
||||
If DASCA is installed using Java 8, there should be 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 location of the Java JDK. The JDK used
|
||||
as part of the static analysis is configured in the `wala.properties`
|
||||
file, e.g.
|
||||
The dataflow analysis can be configured in various ways in the
|
||||
`com.logicalhacking.dasca.dataflow/config/main.config` file. Most importantly,
|
||||
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 location of the Java JDK. The JDK used as part of the static
|
||||
analysis is configured in the file
|
||||
`com.logicalhacking.dasca.dataflow/config/main.config`, e.g.
|
||||
|
||||
``` sh
|
||||
cd DASCA/
|
||||
echo "java_runtime_dir = <PATH-TO-JDK>" >> externals/WALA/com.ibm.wala.core/dat/wala.properties
|
||||
echo "java_runtime_dir = <PATH-TO-JDK>" >> ./com.logicalhacking.dasca.dataflow/config/main.config
|
||||
```
|
||||
|
||||
Don't forget to adjust the path to the Java JDK accordingly, i.e.,
|
||||
|
@ -76,6 +77,7 @@ using `File -> Import -> Gradle -> Existing Gradle Projects`:
|
|||
2. Import all offered projects
|
||||
|
||||
|
||||
|
||||
## Team
|
||||
|
||||
Main contact: [Achim D. Brucker](http://www.brucker.ch/)
|
||||
|
|
|
@ -26,3 +26,21 @@ test {
|
|||
exclude '**/Test0*.class'
|
||||
exclude '**/Test1*.class'
|
||||
}
|
||||
|
||||
task copyConfigIfNotExists {
|
||||
if (!file('config/main.config').exists())
|
||||
copy {
|
||||
from("config")
|
||||
into("config")
|
||||
include("main.config.in")
|
||||
rename("main.config.in", "main.config")
|
||||
}
|
||||
copy {
|
||||
from("config")
|
||||
into("bin/config")
|
||||
include("main.config.in")
|
||||
rename("main.config.in", "main.config")
|
||||
}
|
||||
}
|
||||
|
||||
build.dependsOn(copyConfigIfNotExists)
|
||||
|
|
Loading…
Reference in New Issue