ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-01-07 13:38:47 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

update documentation to indicate that LD_LIBRARY_PATH is not (always) needed

Browse Source
This commit is contained in:
Damjan Jovanovic 2013-02-12 11:00:52 -07:00 committed by Joel Dice
parent 86c92e26cb
commit 3812d012a3
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@ -249,12 +249,11 @@ where OpenJDK is installed, e.g.:
This will build Avian as a conventional JVM (e.g. libjvm.so) which This will build Avian as a conventional JVM (e.g. libjvm.so) which
loads its boot class library and native libraries (e.g. libjava.so) loads its boot class library and native libraries (e.g. libjava.so)
from _/usr/lib/jvm/java-7-openjdk/jre_ at runtime. To run an from _/usr/lib/jvm/java-7-openjdk/jre_ at runtime. In this configuration,
application in this configuration, you'll need to make sure the VM is OpenJDK needs to remain installed for Avian to work, and you can run
in your library search path. For example: applications like this:
$ LD_LIBRARY_PATH=build/linux-x86_64-openjdk \ $ build/linux-x86_64-openjdk/avian-dynamic -cp /path/to/my/application \
build/linux-x86_64-openjdk/avian-dynamic -cp /path/to/my/application \
com.example.MyApplication com.example.MyApplication
Alternatively, you can enable a stand-alone build using OpenJDK by Alternatively, you can enable a stand-alone build using OpenJDK by