From d3abb447a118aecf23afddbec9b83a61ae8d1670 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Wed, 28 Nov 2018 16:02:21 +0100 Subject: Ranch 1.7.1 and Cowboy 2.6.1 --- docs/en/erlang.mk/1/guide/app/index.html | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'docs/en/erlang.mk/1/guide/app') diff --git a/docs/en/erlang.mk/1/guide/app/index.html b/docs/en/erlang.mk/1/guide/app/index.html index 13875dda..205542e0 100644 --- a/docs/en/erlang.mk/1/guide/app/index.html +++ b/docs/en/erlang.mk/1/guide/app/index.html @@ -74,6 +74,20 @@ http://www.gnu.org/software/src-highlite -->

It will work regardless of your project: OTP applications, library applications, NIFs, port drivers or even releases. Erlang.mk also automatically downloads and compiles the dependencies for your project.

All this is possible thanks to a combination of configuration and conventions. Most of the conventions come from Erlang/OTP itself so any seasoned Erlang developers should feel right at home.

+

Erlang.mk supports multi-threaded building. Parallel execution is supported for all targets. To execute Erlang.mk in parallel the -j option must be used:

+
+
$ make -j8
+
+

The MAKEFLAGS variable can be used to enable parallel building permanently on your system. It can be set in your .zshrc, .bashrc or equivalent file.

+
+
MAKEFLAGS="-j8"
+

What to build

Erlang.mk gives you control over three steps of the build process, allowing you to do a partial build if needed.

A build has three phases: first any dependency is fetched and built, then the project itself is built and finally a release may be generated when applicable. A release is only generated for projects specifically configured to do so.

-- cgit v1.2.3