@@ -37,6 +37,33 @@ Either way, you will find the built JAR files in the "target" folder of the resp
3737dependencies that are required for the build. Unless you need to build FlowDroid on a machine without an Internet connection,
3838thing should be pretty easy.
3939
40+ ## Running The Command-Line Tool
41+
42+ If you want to use the command-line tool to run the data flow tracker, you can use the following command:
43+
44+ ```
45+ java -jar soot-infoflow-cmd/target/soot-infoflow-cmd-jar-with-dependencies.jar \
46+ -a <APK File> \
47+ -p <Android JAR folder> \
48+ -s <SourcesSinks file>
49+ ```
50+
51+ The Android JAR folder is the "platforms" directory inside your Android SDK installation folder. The definition file for sources
52+ and sinks defines what shall be treated as a source of sensitive information and what shall be treated as a sink that can possibly
53+ leak sensitive data to the outside world. These definitions are specific to your use case. However, if you are looking for privacy
54+ issues, you can use our default file "SourcesAndSinks.txt" in the "soot-infoflow-android" folder as a starting point.
55+
56+ For finding out about the other options of the command-line tool, you can run the tool with the "--help" option or have a look at
57+ the MainClass.initializeCommandLineOptions()" method in the source code (module soot-infoflow-cmd).
58+
59+ ## Using FlowDroid as a library
60+
61+ If you want to include FlowDroid as a library into your own solution, you can directly reference the respective JAR files. If you
62+ use Maven, you can add FlowDroid as a reference and have Maven resolve all required components. Depending on what you want to analyze
63+ (Android apps or Java programs), your dependencies may vary.
64+
65+ In this section, we will collect code and configuration snippets for common tasks with FlowDroid.
66+
4067## Publications
4168
4269If you want to read the details on how FlowDroid works, <a href =" http://tuprints.ulb.tu-darmstadt.de/5937/ " >the PhD thesis of
0 commit comments