aboutsummaryrefslogtreecommitdiff
path: root/documentation/embedded-building.md
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/embedded-building.md')
-rw-r--r--documentation/embedded-building.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/embedded-building.md b/documentation/embedded-building.md
index 7b3f7d1..36f5ba2 100644
--- a/documentation/embedded-building.md
+++ b/documentation/embedded-building.md
@@ -38,7 +38,7 @@ This section details the procedure for linux-based target platforms.
In your scala/java application, treat flow as if it were a pure scala/java library and build your application with flow as a usual dependency. However, when running your application or any other application that relies on it, the native library must be included in java's library path. To do so, you have several options:
- Per application:
- - Run java with the command-line option -Djava.library.path=".:/home/<folder containing libflow.so>". E.g. ```java -Djava.library.path=".:/home/<folder containing libflow.so>" -jar your-app.jar```
+ - Run java with the command-line option -Djava.library.path="\<folder containing libflow.so\>". For example, if the native library is in the current directory, ```java -Djava.library.path="." -jar your-app.jar```
- Run your program by prepending LD_LIBRARY_PATH=<folder containing libflow.so> to the command. E.g ```LD_LIBRARY_PATH=<folder containing libflow.so> java -jar your-app.jar```
- System- or user-wide: