-
-
Notifications
You must be signed in to change notification settings - Fork 708
Building Soot from the Command Line (Recommended)
Note that unless you are directly working on the Soot source code (adding features, fixing bugs, etc.), you are recommended to use the nightly builds https://soot-build.cs.uni-paderborn.de/public/origin/develop/soot/soot-develop/build/
- Download the Java Development Kit from the following link: http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
- Install Maven on your machine
Soot's nexus server https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/ is reachable via https using let's encrypt certificates. Some older java versions do not include them out-of-the-box.
Thus, we recommend using java >= 1.8.0_144.
The first step is to download Soot latest develop branch.
git clone https://github.com/Sable/soot.git
git checkout develop
In order to build a Soot jar containing Soot's core classes run
mvn clean compile package
.
The resulting jar is saved as target/sootclasses-trunk.jar
.
By default, maven does not include any dependencies in the resulting jar file target/sootclasses-trunk.jar
but defines them in the file sootclasses-trunk.jar:META-INF/maven/pom.xml.
If you need a full soot jar including all dependencies run mvn clean compile assembly:single
.
The resulting jar file target/sootclasses-trunk-jar-with-dependencies.jar
includes all dependencies.
Also check out Soot's webpage.
NOTE: If you find any bugs in those tutorials (or other parts of Soot) please help us out by reporting them in our issue tracker.
- Home
- Getting Help
- Tutorials
- Reference Material
- General Notions
- Getting Started
- A Few Uses of Soot
- Using Soot as a Command-Line Tool
- Using the Soot Eclipse Plugin
- Using Soot as a Compiler Framework
- Building Soot
- Coding Conventions
- Contributing to Soot
- Updating the Soot Web Page
- Reporting Bugs
- Preparing a New Soot Release