From 917a6bc5d88d765ec6d80c8ccce108849b3c4f78 Mon Sep 17 00:00:00 2001 From: Jakob Odersky Date: Mon, 24 Feb 2014 10:28:29 +0100 Subject: Update embedded-building.md --- documentation/embedded-building.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'documentation/embedded-building.md') 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/". E.g. ```java -Djava.library.path=".:/home/" -jar your-app.jar``` + - Run java with the command-line option -Djava.library.path="\". 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= to the command. E.g ```LD_LIBRARY_PATH= java -jar your-app.jar``` - System- or user-wide: -- cgit v1.2.3