From e3346482723a150ddab8d9f949195ec019dcfbb3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?=
Date: Wed, 18 Nov 2015 17:45:40 +0100
Subject: Update user guide
---
guide/ch06.html | 19 ++++++++++---------
guide/index.html | 2 +-
2 files changed, 11 insertions(+), 10 deletions(-)
(limited to 'guide')
diff --git a/guide/ch06.html b/guide/ch06.html
index c307549..e067443 100644
--- a/guide/ch06.html
+++ b/guide/ch06.html
@@ -50,20 +50,21 @@ two of them.
The commands detailed in this section are most useful after
you have a successful build as they allow you to quickly
redo a step instead of going through everything. This is
especially useful for large projects or projects that end
-up generating releases.
You can build your application specifically, without
-looking at handling dependencies or generating a release,
-by running the following command:
$ make app
This command is very useful if you have a lot of dependencies
+up generating releases.
You can build your application and dependencies without
+generating a release by running the following command:
$ make app
To build your application without touching dependencies
+at all, you can use the SKIP_DEPS
variable:
$ 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.
Note that this command may fail if a required dependency
is missing.
You can build all dependencies, and nothing else, by
running the following command:
$ make deps
This will fetch and compile all dependencies and their
dependencies, recursively.
Packages and dependencies are covered
-in the next chapter.
You can generate the release, skipping the steps for building
-the application and dependencies, by running the following
-command:
$ make rel
This command can be useful if nothing changed except the
-release configuration files.
Consult the 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.
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:
$ make rel
Consult the Releases chapter for more
+information about what releases are and how they are generated.