From e1e76745e6719e0aa05b634a65500d4f8b8e4a7b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Mon, 15 May 2017 16:54:40 +0200 Subject: Update user guide --- guide/plugins_usage.html | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) (limited to 'guide/plugins_usage.html') diff --git a/guide/plugins_usage.html b/guide/plugins_usage.html index eb8bc2f..f6d2c4b 100644 --- a/guide/plugins_usage.html +++ b/guide/plugins_usage.html @@ -79,7 +79,16 @@ BUILD_DEPS = common_deps DEP_EARLY_PLUGINS = common_deps
# In the plugin's early-plugins.mk
 DEPS += cowboy
 TEST_DEPS = ct_helper
-dep_ct_helper = git https://github.com/ninenines/ct_helper master
Prev Up Next
 Home 
+dep_ct_helper = git https://github.com/ninenines/ct_helper master

22.5. Loading plugins local to the application

If the Erlang.mk plugin lives in the same directory or repository as your +application or library, then you can load it exactly like an external +plugin: the dependency name is simply the name of your application or +library.

For example, the following Makefile loads a plugin in the mk +subdirectory:

DEP_PLUGINS = $(PROJECT)/mk/dist.mk

This also works with early-stage plugins:

DEP_EARLY_PLUGINS = $(PROJECT)/mk/variables.mk

Like external plugins, if you do not specify the path to the plugin, it +defaults to plugins.mk or early-plugins.mk, located at the root of +your application:

# Loads ./early-plugins.mk
+DEP_EARLY_PLUGINS = $(PROJECT)
+# Loads ./plugins.mk
+DEP_PLUGINS = $(PROJECT)
Prev Up Next
 Home 
-- cgit v1.2.3