File tree Expand file tree Collapse file tree 2 files changed +18
-1
lines changed Expand file tree Collapse file tree 2 files changed +18
-1
lines changed Original file line number Diff line number Diff line change @@ -11,7 +11,7 @@ defmodule Mix.Project do
11
11
12
12
def project do
13
13
[app: :my_app,
14
- vsn : "0.6.0"]
14
+ version : "0.6.0"]
15
15
end
16
16
end
17
17
@@ -24,6 +24,16 @@ defmodule Mix.Project do
24
24
function in the project, the developer can call `Mix.Project.get!/0`
25
25
which fails with `Mix.NoProjectError` in case a project is not
26
26
defined.
27
+
28
+ ## Erlang projects
29
+
30
+ Mix can be used to manage Erlang projects that don't have any Elixir code. To
31
+ ensure mix tasks work correctly for an Erlang project, `language: :erlang`
32
+ has to be added to `project`.
33
+
34
+ The setting also makes sure Elixir is not added as a dependency to the
35
+ generated .app file or to the escript generated with `mix escript.build`,
36
+ etc.
27
37
"""
28
38
29
39
@ doc false
Original file line number Diff line number Diff line change @@ -56,6 +56,13 @@ defmodule Mix.Tasks.Escript.Build do
56
56
* `:emu_args` - emulator arguments to embed in the escript file.
57
57
Defaults to `""`.
58
58
59
+ There is one project-level option that affects how the escript is generated:
60
+
61
+ * `language: :elixir | :erlang` - set it to `:erlang` for Erlang projects
62
+ managed by mix. Doing so will ensure Elixir is not embedded by default.
63
+ Your app will still be started as part of escript loading, with the
64
+ config used during build.
65
+
59
66
## Example
60
67
61
68
defmodule MyApp.Mixfile do
You can’t perform that action at this time.
0 commit comments