java-bridge: Bindings to the JNI and a high level interface generator.
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.
high level bindings generator
- You can also generate high level bindings using the tools
hs2jthat come along with this package. The tools works in both directions, i.e. you can generate glue code to use existing Java libraries from within Haskell as well as to use Haskell from within Java. This is the most convenient way to deal with a Java library.
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 load
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
FFIJNI_LIBJVM. This 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
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,
Foreign.Java.JNI.Safe, and Foreign.Java.JNI.Unsafe.
NO_TOOLS. Defaults to
- Do not build the
hs2jexecutables. 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
- Build a set of examples. They are prefixed
java-and located along your haskell executables. Defaults to
Use for example
cabal install -f OSX_FRAMEWORK -f EXAMPLES
cabal configure -f DEBUG.
ISSUES.txt in the tar.gz-package.
[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), bimap (>=0.2.4), containers (>=0.4.2.1), cpphs (>=1.16), directory (>=188.8.131.52), filepath (>=1.3), hinduce-missingh, hint (>=0.3.3.4), java-bridge, mtl (>=2.1.1), multimap (>=1.2), named-records (>=0.5), names (>=0.3.1 && <0.4), split (>=0.2.1.1), strings (>=1.1), syb (>=0.3.6.1), transformers (>=0.3), unix [details]|
|Author||Julian Fleischer <firstname.lastname@example.org>|
|Maintainer||Julian Fleischer <email@example.com>|
|Category||Foreign, Java, JVM, FFI Tools|
|Uploaded||by JulianFleischer at Sat Jun 8 08:28:55 UTC 2013|
|Executables||java-system-properties, java-calculator, h2js, j2hs|
|Downloads||2635 total (19 in the last 30 days)|
|Rating||(no votes yet) [estimated by rule of succession]|
|Status||Docs not available [build log]
All reported builds failed as of 2016-12-21 [all 7 reports]
Hackage Matrix CI
Build only the Core Modules which offer a direct binding to the Java Native Interface.
Do not build the
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.
Build a set of sample executables.
Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info
For package maintainers and hackage trustees