1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
[[escript]]
== 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 xref:relx[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 xref:sfx[self-extracting releases].
=== 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:
[source,bash]
$ make escript ESCRIPT_ZIP=zip
=== Generating an escript
Run the following command to generate an escript:
[source,bash]
$ 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
called `relx` then the escript will be in `./relx`.
You can run the escript as you would any executable:
[source,bash]
$ ./relx
=== Configuration
You can change the name of the escript by setting `ESCRIPT_NAME`.
The name determines both the default output file name and the
entry module containing the function `main/1`.
`ESCRIPT_FILE` can be set if you need a different file name
or location.
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_EMU_ARGS`.
Finally, `ESCRIPT_ZIP` can be set to customize the command used
to create the zip file. Read on for more information.
=== Extra files
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:
[source,make]
----
escript-zip::
$(verbose) $(ESCRIPT_ZIP) $(ESCRIPT_ZIP_FILE) priv/templates/*
----
The `ESCRIPT_ZIP` variable contains the command to run to add
files to the zip archive `ESCRIPT_ZIP_FILE`.
=== Optimizing for size
Erlang.mk will by default compile BEAM files with debug
information. You may want to disable this behavior to obtain
smaller escript files. Simply set `ERLC_OPTS` to a value that
does not include `+debug_info`.
|
