From d2a3f2cedd7c00d0933222aed9c06b3149aa4db4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Wed, 4 Apr 2018 13:13:37 +0200 Subject: Cowboy 2.3.0 --- docs/en/erlang.mk/1/guide/deps/index.html | 62 +++++++++++++++---------------- 1 file changed, 31 insertions(+), 31 deletions(-) (limited to 'docs/en/erlang.mk/1/guide/deps') diff --git a/docs/en/erlang.mk/1/guide/deps/index.html b/docs/en/erlang.mk/1/guide/deps/index.html index f74a5842..98fe2cd5 100644 --- a/docs/en/erlang.mk/1/guide/deps/index.html +++ b/docs/en/erlang.mk/1/guide/deps/index.html @@ -7,7 +7,7 @@ - + Nine Nines: Packages and dependencies @@ -84,7 +84,7 @@ in a single repository.

being added regularly.

To find a package, search for it:

-
@@ -94,7 +94,7 @@ pool and acceptor pool projects.

You can also list everything and use regular command line tools to find what you need, for example:

-
@@ -107,7 +107,7 @@ http://www.gnu.org/software/src-highlite -->

Once you find the package you need, adding it as a dependency to your project is a one-liner:

-
@@ -126,7 +126,7 @@ dependencies.

For example, you could add a parse transform project like this to make it available only at build time:

-
@@ -134,7 +134,7 @@ http://www.gnu.org/software/src-highlite -->

Or you could depend on a C project directly, if you are building a NIF:

-
@@ -153,7 +153,7 @@ Do note that there is no way to choose the version, the application used will be the one already on your system.

You could depend on the Crypto application, for example:

-
@@ -161,7 +161,7 @@ http://www.gnu.org/software/src-highlite -->

Erlang.mk comes with additional types of dependencies. It has TEST_DEPS for dependencies used only for testing:

-
@@ -169,7 +169,7 @@ http://www.gnu.org/software/src-highlite --> dep_ct_helper = git https://github.com/ninenines/ct_helper master

DOC_DEPS for dependencies used only when building documentation:

-
@@ -177,7 +177,7 @@ http://www.gnu.org/software/src-highlite -->

REL_DEPS for dependencies required to build the release, or to include extra applications in the release:

-
@@ -185,7 +185,7 @@ http://www.gnu.org/software/src-highlite -->

And SHELL_DEPS for dependencies to make available when running the make shell command:

-
@@ -198,7 +198,7 @@ chapters.

find the project you are looking for, if you only provide its name. This is this case:

-
@@ -210,7 +210,7 @@ for different reasons.

need to do is to define the dep_$(DEP_NAME)_commit variable. In the case of Cowboy, this would look like this:

-
@@ -223,7 +223,7 @@ too, for example because you want to use your own fork, or simply because the project is missing from the index, you can define the dep_$(DEP_NAME) variable with everything:

-
@@ -307,14 +307,14 @@ You can use any valid commit, tag or branch in that repository for the commit value.

For example, to fetch Cowboy with tag 2.0.0-pre.2 from Git:

-
dep_cowboy = git https://github.com/ninenines/cowboy 2.0.0-pre.2

Or to fetch Ehsa tag 4.0.3 from Mercurial:

-
@@ -323,7 +323,7 @@ http://www.gnu.org/software/src-highlite --> automatically initializes and updates submodules for dependencies, as long as they were added beforehand using git submodule add:

-
@@ -333,7 +333,7 @@ simply because the SVN repository URL can also contain the path and commit.

This would fetch an example project from the trunk:

-
@@ -341,7 +341,7 @@ http://www.gnu.org/software/src-highlite -->

And this would fetch a separate example project from a specific commit:

-
@@ -349,7 +349,7 @@ http://www.gnu.org/software/src-highlite -->

You can copy a directory from your machine using the cp method. It only takes the path to copy from:

-
@@ -357,7 +357,7 @@ http://www.gnu.org/software/src-highlite -->

Finally, you can use a package from the Hex repository:

-
@@ -374,7 +374,7 @@ Or in layman terms, if your dependency is Cowboy, this would become deps/cowboy.

To give an example, this is what the Git method does:

-
@@ -509,7 +509,7 @@ on your system.

To ignore a dependency, simply add it to the IGNORE_DEPS variable:

-
@@ -517,7 +517,7 @@ http://www.gnu.org/software/src-highlite -->

This will only ignore dependencies that are needed for building. It is therefore safe to write:

-
@@ -540,7 +540,7 @@ own dependencies.

if you know you will never use this project as a dependency, = will work. But to avoid it biting you later on, do this:

-
@@ -609,14 +609,14 @@ the application.

For example, to create a full fledged OTP application as a local dependency:

-
$ make new-app in=webchat

Or, the same as an OTP library:

-
@@ -625,7 +625,7 @@ http://www.gnu.org/software/src-highlite --> directory of the project. You do need however to tell Erlang.mk to create the files in the correct application:

-
@@ -724,7 +724,7 @@ Other projects with no Makefile are left untouched.

You can disable the replacing of the erlang.mk file by defining the NO_AUTOPATCH_ERLANG_MK variable:

-
@@ -732,7 +732,7 @@ http://www.gnu.org/software/src-highlite -->

You can also disable autopatch entirely for a few select projects using the NO_AUTOPATCH variable:

-
@@ -748,7 +748,7 @@ include being somewhere with no connection to download them, or perhaps a peculiar setup.

A typical usage would be:

-
-- cgit v1.2.3