Escripts are an alternative to release. They are meant to be used for small command line executables written in Erlang.
They are not self-contained, unlike releases. Erlang must be installed for them to run. This however means that they are fairly small compared to releases.
For self-contained executables, check self-extracting releases.
p7zip by default to generate the escript
archive. Make sure it is installed. On most systems the
package is named
p7zip; on Ubuntu you need
p7zip is unavailable,
zip may be used by setting
ESCRIPT_ZIP variable. For example:
$ make escript ESCRIPT_ZIP=zip
Run the following command to generate an escript:
$ make escript
This will by default create an escript with the same name as
the project, in the project’s directory. If the project is
relx then the escript will be in
You can run the escript as you would any executable:
You can change the name of the escript by setting
The name determines both the default output file name and the
entry module containing the function
ESCRIPT_FILE can be set if you need a different file name
The escript header can be entirely customized. The first line
is the shebang, set by
ESCRIPT_SHEBANG. The second line is
a comment, set by
ESCRIPT_COMMENT. The third line is the
arguments the VM will use when running the escript, set by
ESCRIPT_ZIP can be set to customize the command used
to create the zip file. Read on for more information.
Generating an escript is a two-part process. First, a zip file is created with the contents of the escript. Then a header is added to this file to create the escript.
It is possible to add commands that will be executed between the two steps. You can for example add extra files to the zip archive:
escript-zip:: $(verbose) $(ESCRIPT_ZIP) $(ESCRIPT_ZIP_FILE) priv/templates/*
ESCRIPT_ZIP variable contains the command to run to add
files to the zip archive