From 8c599e4559add29eaa1cd644633bd48394b60f00 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Tue, 25 Apr 2017 17:46:53 +0200 Subject: Update user guide --- guide/deps.html | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) (limited to 'guide/deps.html') diff --git a/guide/deps.html b/guide/deps.html index d5b8f13..3ab003c 100644 --- a/guide/deps.html +++ b/guide/deps.html @@ -199,9 +199,18 @@ They are not autopatched 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.

    If there is a conflict between a local dependency and a +

    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; an error will be triggered when trying to fetch the conflicting remote dependency.

    To start using dependencies local to the repository, simply -- cgit v1.2.3