Rebar3 is the standard build tool within the Erlang community. It essentially integrates many of the other tools shipping with Erlang along with a few open-source ones, and makes them all work under a unified project structure.
Rebar3 relies on Erlang already being present in your system in order to run. If Erlang runs there, Rebar3 should run there as well.
See the Adopting Erlang section Installing Erlang/OTP for detailed steps on how to install Erlang for Windows, MacOS, Linux and FreeBSD.
Installing from the Rebar3 escript
Download the latest stable release as an executable escript. While the script version of Rebar3 is portable and usable from anywhere, it is advised not to keep it in your project’s repository and to install it globally, for your entire system. Regardless of which recent Erlang version you have installed, Rebar3 should be fully compatible with it.
One downside of the escript however is that it is a bit slower than a regular Erlang program. We recommend installing a fully compiled form of Rebar3, which Rebar3 itself can do for you:
$ ./rebar3 local install ===> Extracting rebar3 libs to ~/.cache/rebar3/lib... ===> Writing rebar3 run script ~/.cache/rebar3/bin/rebar3... ===> Add to $PATH for use: export PATH=$PATH:~/.cache/rebar3/bin
Be sure to follow the instructions the command outputs and add the executable to your system’s
$PATH, such as by calling
export PATH=$PATH:~/.cache/rebar3/bin. You can then delete the
rebar3 escript you used to run
When a new stable release of
rebar3 is available, you can simply run
rebar3 local upgrade and the new version will be fetched and installed the same way:
$ rebar3 local upgrade ===> Extracting rebar3 libs to ~/.cache/rebar3/lib... ===> Writing rebar3 run script ~/.cache/rebar3/bin/rebar3... ===> Add to $PATH for use: export PATH=$PATH:~/.cache/rebar3/bin
Windows users who want to use the code from PowerShell or
cmd.exe (rather than a terminal emulator) must ensure that a
rebar3.cmd file is added:
@echo off setlocal set rebarscript=%~f0 escript.exe "%rebarscript:.cmd=%" %*
Then add the directory where the file has been saved to the system
If you want to change the default path (
C:\Users\<user>) you can set an environment variable for
REBAR_CACHE_DIR pointing to a directory of your liking.
Installing from Source
rebar3 project’s repo is hosted on GitHub and comes with a
bootstrap script for building from source. This form is likely to cause fewer issues for Windows users, since building from source will generate the wrapper scripts required to work well in both
cmd.exe and PowerShell environments:
$ git clone https://github.com/erlang/rebar3.git $ cd rebar3 $ ./bootstrap
This will compile a
rebar3 escript to the top level of the
rebar3 directory, which you can then install globally:
$ ./rebar3 local install
Do note that if you are planning to work with multiple Erlang versions on the same machine, you will want to build Rebar3 with the oldest one of them. The three newest major Erlang releases are supported at any given time: if the newest version is OTP-24, building with versions as old as OTP-22 will be supported, and produce an executable that will work with those that follow.
Creating a New Project
Rebar3 offers templates that will ensure your Erlang project fits into a regular OTP structure:
$ rebar3 new umbrella myproj ===> Writing apps/myproj/src/myproj_app.erl ===> Writing apps/myproj/src/myproj_sup.erl ===> Writing apps/myproj/src/myproj.app.src ===> Writing rebar.config ===> Writing config/sys.config ===> Writing config/vm.args ===> Writing .gitignore ===> Writing LICENSE ===> Writing README.md
The OTP structure is part of the basic contract Rebar3 expects; following it will guarantee a much better time than doing otherwise.
You can see Basic Usage to learn more on how to use
rebar3, and follow it with Workflow for broader usage.