From 4684b443bbe71bd9b7acd7a4b5aec5160031ae71 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Mon, 4 Jun 2018 12:04:40 +0200 Subject: Update user guide --- guide/escript.html | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) (limited to 'guide/escript.html') diff --git a/guide/escript.html b/guide/escript.html index 77cffef..7ea67a2 100644 --- a/guide/escript.html +++ b/guide/escript.html @@ -34,11 +34,9 @@ div.navfooter{margin-bottom:1em}
Prev   Next

Chapter 11. Escripts

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 -Chapter 9, Releases. +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 -Chapter 10, Self-extracting releases.

11.1. Requirements

Erlang.mk uses p7zip by default to generate the escript +that they are fairly small compared to releases.

For self-contained executables, check self-extracting releases.

11.1. Requirements

Erlang.mk uses 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-full.

If p7zip is unavailable, zip may be used by setting the ESCRIPT_ZIP variable. For example:

$ make escript ESCRIPT_ZIP=zip

11.2. Generating an escript

Run the following command to generate an escript:

$ make escript

This will by default create an escript with the same name as -- cgit v1.2.3