llvm-ffi
Version 13.0 revision 0 uploaded by HenningThielemann.
Package meta
- Synopsis
- FFI bindings to the LLVM compiler toolkit.
- Description
FFI bindings to the LLVM compiler toolkit.
Installation cannot be done fully automatically. It would require Cabal code that is bound to certain Cabal versions and is prone to fail. We give several non-automatic ways that also allow you to choose a particular LLVM version.
First possibility is to point Cabal to the LLVM installation directories manually. It is recommended to add options to your global
.cabal/config
:extra-include-dirs: /usr/lib/llvm-13/include extra-lib-dirs: /usr/lib/llvm-13/lib
This works for both
v1-build
andv2-build
. The shown paths work for Debian and Ubuntu using the LLVM repositories at https://apt.llvm.org/. You can obtain them withllvm-config-13 --includedir --libdir
You can choose specific LLVM versions per project. For
v1-builds
it works like so:cabal install -fllvm900 --extra-include-dirs=$(llvm-config-9 --includedir) --extra-lib-dirs=$(llvm-config-9 --libdir) yourpackage
For Nix-style build you must add some options to the
cabal.project.local
file of your LLVM-related project:package llvm-ffi flags: +llvm900 extra-include-dirs: /usr/lib/llvm-9/include extra-lib-dirs: /usr/lib/llvm-9/lib
The second way uses
pkg-config
. You can store above paths permanently in apkg-config
file likellvm.pc
. The optimal way would be if LLVM installations or GNU/Linux distributions would contain such a file, but they don't. Instead, you may generate it using thellvm-pkg-config
package or write one manually. Then you runcabal install -fpkgConfig
We try to stay up to date with LLVM releases. The current version of this package is compatible with LLVM 3.9-13. Please understand that the package may or may not work against older LLVM releases.
Warning for inplace builds: Re-configuring the package using, say
-fllvm600
, and re-buildung it might result in corrupt code. You must make sure that the stuff incbits
is re-compiled. Cabal or GHC may forget about that. You are safe if you runcabal clean
.Caution: Ugly crashes can occur if you have configured paths for LLVM version X in
.cabal/config
and try to buildllvm-ffi
for a different LLVM version Y. Counterintuitively, global search paths have higher precedence than local ones: https://github.com/haskell/cabal/issues/7782. But that does not simply mean that the local configuration is ignored completely. Instead the local library file is found, because its name libLLVM-Y.so is unique, whereas the include file names clash, thus the ones from the global include directory are used.- Author
- Henning Thielemann, Bryan O'Sullivan, Lennart Augustsson
- Bug reports
- n/a
- Category
- Compilers/Interpreters, Code Generation
- Copyright
- n/a
- Homepage
- http://haskell.org/haskellwiki/LLVM
- Maintainer
- Henning Thielemann <llvm@henning-thielemann.de>
- Package URL
- n/a
- Stability
- experimental