The java-bridge package
This package offers bindings to the Java Native Interface and a high level interface generator.
low level bindings to the JNI
- The low level bindings are located in Foreign.Java.JNI.Safe and Foreign.Java.JNI.Unsafe. When using these bindings you will have to deal with pointers and manage global references manually.
medium level interface
- The medium level interface is located in Foreign.Java. It offers an abstraction over the JNI, i.e. you will not have to deal with pointers explicitly nor do you need to manually do conversions between native types and Haskell types. Also references will automatically be released by the Haskell runtime when no longer needed. You will still need to manually lookup classes and methods in order to use them.
INSTALLATION / USAGE
It should suffice to do
cabal install (or
cabal install java-bridge when installing from
hackageDB). /You need to have a JDK installed prior to
installing this library/.
Setup will try to find the location of your java
installation automatically. This is needed in order to
libjvm. Note that this library is loaded
dynamically, which means that linking errors might not
show up during installation.
You can specify the location of
libjvm manually using
the environment variable
environment variable is consulted by
Setup.hs as well
as by the library each time
libjvm is loaded - which
means that you can override the path to
libjvm at any
time. The function
Foreign.Java.JNI.Safe will tell you what path to
libjvm has been set during compilation of the library.
FUN WITH (cabal-) FLAGS
The following cabal flags are available to you for configuring your installation:
- Build only the Core Modules which offer a
direct binding to the Java Native Interface.
The core modules are Foreign.Java.JNI,
NO_TOOLS. Defaults to
- Enable a debug build. Defaults to
- Build the library with special support for
Cocoa on Mac OS X (you will not be able to
use AWT or Swing without). Defaults to
Trueon Darwin (OS X).
- Use the JavaVM framework on MacOS X instead
of loading the dynamic library. Defaults to
False. Enable this flag if building on your OS X machine fails. Defaults to
Use for example
cabal install -f OSX_FRAMEWORK -f EXAMPLES
cabal configure -f DEBUG.
[Skip to Readme]
|Versions||0.9, 0.99, 0.20130602, 0.20130606, 0.20130606.1, 0.20130606.2, 0.20130606.3|
|Dependencies||base (>=4.5 && <5), cpphs (>=1.16), directory (>=184.108.40.206), filepath (>=1.3), hx (>=0.4), mtl (>=2.1.1), strings (>=1.1), transformers (>=0.3), unix [details]|
|Author||Julian Fleischer <email@example.com>|
|Maintainer||Julian Fleischer <firstname.lastname@example.org>|
|Category||Foreign, Java, JVM, FFI Tools|
|Uploaded||Mon Jun 24 18:40:15 UTC 2013 by JulianFleischer|
|Downloads||2615 total (25 in the last 30 days)|
|Rating||(no votes yet) [estimated by rule of succession]|
|Status||Docs uploaded by user
Build status unknown [no reports yet]
Hackage Matrix CI
Build only the Core Modules which offer a direct binding to the Java Native Interface.
Enable a debug build.
Build the library with special support for Cocoa on Mac OS X.
Use the JavaVM framework on MacOS X instead of loading the dynamic library.
Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info
For package maintainers and hackage trustees