Documentation can be browsed on Read the Docs or GitHub.
Both for using an up-to-date version of Goblint or developing it, the best way is to install from source by cloning this repository.
- Install opam.
- Make sure the following are installed:
git
,patch
,m4
,autoconf
,libgmp-dev
,libmpfr-dev
andpkg-config
. - Run
make setup
to install OCaml and dependencies via opam. - Run
make
to build Goblint itself. - Run
make install
to install Goblint into the opam switch for usage via switch'sPATH
.
- Install GCC with
brew install gcc
(first runxcode-select --install
if you don't want to build it from source). Goblint requires GCC while macOS's defaultcpp
is Clang, which will not work. - ONLY for M1 (ARM64) processor: homebrew changed its install location from
/usr/local/
to/opt/homebrew/
. For packages to find their dependecies executesudo ln -s /opt/homebrew/{include,lib} /usr/local/
. - Continue using Linux instructions (the formulae in brew for
patch
,libgmp-dev
,libmpfr-dev
aregpatch
,gmp
,mpfr
, respectively).
- Install WSL2. Goblint is not compatible with WSL1.
- Continue using Linux instructions in WSL.
- opam. Install opam and run
opam install goblint
. - devcontainer. Select "Reopen in Container" in VS Code and continue with
make
using Linux instructions in devcontainer. - Docker (GitHub Container Registry). Run
docker pull ghcr.io/goblint/analyzer:latest
(or:nightly
). - Docker (repository). Clone and run
docker build -t goblint .
. - Vagrant. Clone and run
vagrant up && vagrant ssh
.
To confirm that building worked, you can try running Goblint as follows:
./goblint tests/regression/04-mutex/01-simple_rc.c
To confirm that installation into the opam switch worked, you can try running Goblint as follows:
goblint tests/regression/04-mutex/01-simple_rc.c
To confirm that the Docker container worked, you can try running Goblint as follows:
docker run -it --rm -v $(pwd):/data goblint /data/tests/regression/04-mutex/01-simple_rc.c
If pulled from GitHub Container Registry, use the container name ghcr.io/goblint/analyzer:latest
(or :nightly
) instead.
For further information, see documentation.