Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Gerbil uses a few environment variables, which affect the behaviour of the runtime and toolchain:
This is the root of your Gerbil installation.
The runtime expects the gerbil system modules to be located in
$GERBIL_HOME/lib, which is set as the first component of the runtime
load path. The compiler also expects to find system static compilation
This variable must be set for dynamic executables to be able to load
gxc can deduce it automatically from their
installation path if it's not set.
This is the root of your Gerbil workspace, which is the read-write
component of the system. If it's not set, then it defaults to
The runtime adds
$GERBIL_PATH/lib as the second component of the
runtime load path.
The toolchain uses
$GERBIL_PATH as default artifact output directory:
gxcoutputs compiled modules to
$GERBIL_PATH/lib, unless otherwise instructed.
:std/makeoutputs compiled modules to
$GERBIL_PATH/liband binaries to
$GERBIL_PATH/bin, unless otherwise instructed.
This is colon separated a list of directories to be appended to the runtime load path. You can use this for loading site specific libraries. By default it's unset, which is equivalent to an empty value.
This is a directory that can be used by the compiler to cache intermediate
files during compilation of executables. If it's not set, it defaults to