aboutsummaryrefslogtreecommitdiffstats
path: root/doc/src/guide
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/guide')
-rw-r--r--doc/src/guide/app.asciidoc28
1 files changed, 16 insertions, 12 deletions
diff --git a/doc/src/guide/app.asciidoc b/doc/src/guide/app.asciidoc
index 1320577..b2854de 100644
--- a/doc/src/guide/app.asciidoc
+++ b/doc/src/guide/app.asciidoc
@@ -46,13 +46,18 @@ up generating releases.
==== Application
-You can build your application specifically, without
-looking at handling dependencies or generating a release,
-by running the following command:
+You can build your application and dependencies without
+generating a release by running the following command:
[source,bash]
$ make app
+To build your application without touching dependencies
+at all, you can use the `SKIP_DEPS` variable:
+
+[source,bash]
+$ make app SKIP_DEPS=1
+
This command is very useful if you have a lot of dependencies
and develop on a machine with slow file access, like the
Raspberry Pi and many other embedded devices.
@@ -76,22 +81,21 @@ in the next chapter.
==== Release
-You can generate the release, skipping the steps for building
-the application and dependencies, by running the following
-command:
+It is not possible to build the release without at least
+building the application itself, unless of course if there's
+no application to begin with.
+
+To generate the release, `make` will generally suffice with
+a normal Erlang.mk. A separate target is however available,
+and will take care of building the release, after building
+the application and all dependencies:
[source,bash]
$ make rel
-This command can be useful if nothing changed except the
-release configuration files.
-
Consult the link:relx.asciidoc[Releases] chapter for more
information about what releases are and how they are generated.
-Note that this command may fail if a required dependency
-is missing.
-
=== Application resource file
When building your application, Erlang.mk will generate the