aboutsummaryrefslogtreecommitdiffstats
path: root/doc/src/guide/deps.asciidoc
diff options
context:
space:
mode:
authorJeffrey Griffin <[email protected]>2017-02-17 11:16:57 -0800
committerLoïc Hoguin <[email protected]>2017-04-25 15:13:48 +0200
commit750bdd359b0db9fc665d9a371b65ec7bb5d037c7 (patch)
tree34701e095c0231285db46b7e062ae9bbf8e372d8 /doc/src/guide/deps.asciidoc
parent9ca56c45850709473f60bf5de71008a747d4e27b (diff)
downloaderlang.mk-750bdd359b0db9fc665d9a371b65ec7bb5d037c7.tar.gz
erlang.mk-750bdd359b0db9fc665d9a371b65ec7bb5d037c7.tar.bz2
erlang.mk-750bdd359b0db9fc665d9a371b65ec7bb5d037c7.zip
compile apps in the right order by looking at their LOCAL_DEPS
we also use LOCAL_DEPS at the top-level, if it exists, to determine which local apps to compile, in the interest of saving compile time for projects that have many apps and multiple release configurations
Diffstat (limited to 'doc/src/guide/deps.asciidoc')
-rw-r--r--doc/src/guide/deps.asciidoc17
1 files changed, 14 insertions, 3 deletions
diff --git a/doc/src/guide/deps.asciidoc b/doc/src/guide/deps.asciidoc
index 723deb0..7b36c91 100644
--- a/doc/src/guide/deps.asciidoc
+++ b/doc/src/guide/deps.asciidoc
@@ -397,9 +397,20 @@ They work exactly the same as remote dependencies, except:
* They are not deleted on `make distclean`
* They are not automatically added to the application resource file
-To properly fill the application resource file, you will
-need to define the `LOCAL_DEPS` variable for each relevant
-application, the same as for OTP applications.
+To properly fill the application resource file and compile apps in
+the right order, you will need to define the `LOCAL_DEPS` variable
+for each relevant application, the same as for OTP applications. Apps
+can depend on each other in this way, and their compilation order
+will follow the same rules as regular dependencies in `DEPS`.
+
+The top-level `LOCAL_DEPS` variable, if defined, will determine which
+apps (along with their dependencies) to build, and also which apps
+should be added to the top-level application resource file, if there
+is one. This may be useful, for example, for specifying a different
+set of apps to build for different releases. If `LOCAL_DEPS` is not
+defined, then all apps in the '$(APPS_DIR)' will be built, but none
+will be automatically added to the top-level application resource
+file.
If there is a conflict between a local dependency and a
remote dependency, then the local dependency always wins;