diff options
Diffstat (limited to 'docs/en/erlang.mk/1/guide/kerl/index.html')
| -rw-r--r-- | docs/en/erlang.mk/1/guide/kerl/index.html | 88 |
1 files changed, 20 insertions, 68 deletions
diff --git a/docs/en/erlang.mk/1/guide/kerl/index.html b/docs/en/erlang.mk/1/guide/kerl/index.html index 4fc8f102..eb9fe097 100644 --- a/docs/en/erlang.mk/1/guide/kerl/index.html +++ b/docs/en/erlang.mk/1/guide/kerl/index.html @@ -62,84 +62,36 @@ <h1 class="lined-header"><span>OTP version management</span></h1> -<div class="paragraph"><p>Erlang.mk comes with integrated support for -<a href="https://github.com/kerl/kerl">Kerl</a>, a shell script that -automates the downloading, building and installing of -Erlang/OTP. It can be used to easily build a specific -Erlang/OTP version (with or without custom build options) -or maintain different versions side by side.</p></div> -<div class="sect1"> +<p>Erlang.mk comes with integrated support for <a href="https://github.com/kerl/kerl">Kerl</a>, a shell script that automates the downloading, building and installing of Erlang/OTP. It can be used to easily build a specific Erlang/OTP version (with or without custom build options) or maintain different versions side by side.</p> <h2 id="_erlang_versions">Erlang versions</h2> -<div class="sectionbody"> -<div class="paragraph"><p>Erlang.mk uses the Git tags from Erlang/OTP to identify -OTP versions. The most recent tag at the time of writing -is <code>OTP-20.0.4</code>, which is a patch release of <code>OTP-20.0</code>. -A patch release is a non-official release containing a -few fixes on top of the official release.</p></div> -<div class="paragraph"><p>Older versions used a slightly different versioning scheme -and tag format, for example: <code>OTP_R16B03</code>. Beware though, -there also was an <code>OTP_R16B03-1</code> release that fixed a -critical issue in the initial release.</p></div> -<div class="paragraph"><p>The README file for all official Erlang/OTP releases can -be found on <a href="http://www.erlang.org/downloads">erlang.org</a>. -To obtain information about patch releases when they are -released you need to be subscribed to the -<a href="http://erlang.org/mailman/listinfo/erlang-questions">erlang-questions mailing list</a>.</p></div> -</div> -</div> -<div class="sect1"> +<p>Erlang.mk uses the Git tags from Erlang/OTP to identify OTP versions. The most recent tag at the time of writing is <code>OTP-20.0.4</code>, which is a patch release of <code>OTP-20.0</code>. A patch release is a non-official release containing a few fixes on top of the official release.</p> +<p>Older versions used a slightly different versioning scheme and tag format, for example: <code>OTP_R16B03</code>. Beware though, there also was an <code>OTP_R16B03-1</code> release that fixed a critical issue in the initial release.</p> +<p>The README file for all official Erlang/OTP releases can be found on <a href="http://www.erlang.org/downloads">erlang.org</a>. To obtain information about patch releases when they are released you need to be subscribed to the <a href="http://erlang.org/mailman/listinfo/erlang-questions">erlang-questions mailing list</a>.</p> <h2 id="otp_version_pinning">OTP version pinning</h2> -<div class="sectionbody"> -<div class="paragraph"><p>Erlang.mk can use a specific version of Erlang/OTP when -interacting with your project. This can be very useful -when you are working with a team because you can define -the version you need in the Makefile and Erlang.mk will -ensure this version is used by everyone in your team.</p></div> -<div class="paragraph"><p>To pin the version all you need to do is to set the -<code>ERLANG_OTP</code> variable in your Makefile before including -Erlang.mk. For example, to use <code>OTP-20.0.4</code>:</p></div> -<div class="listingblock"> -<div class="content"><!-- Generator: GNU source-highlight +<p>Erlang.mk can use a specific version of Erlang/OTP when interacting with your project. This can be very useful when you are working with a team because you can define the version you need in the Makefile and Erlang.mk will ensure this version is used by everyone in your team.</p> +<p>To pin the version all you need to do is to set the <code>ERLANG_OTP</code> variable in your Makefile before including Erlang.mk. For example, to use <code>OTP-20.0.4</code>:</p> +<div class="listingblock"><div class="content"><!-- Generator: GNU source-highlight 3.1.8 by Lorenzo Bettini http://www.lorenzobettini.it http://www.gnu.org/software/src-highlite --> -<pre><tt><span style="color: #009900">ERLANG_OTP =</span> OTP-20.0.4 - -include erlang.mk</tt></pre></div></div> -<div class="paragraph"><p>The next time you run <code>make</code> Erlang.mk will build and -use the version you configured.</p></div> -<div class="paragraph"><p>Note that there has been reports that this functionality -is not compatible with the <code>.ONESHELL</code> feature from -GNU Make.</p></div> -</div> -</div> -<div class="sect1"> +<pre><tt><font color="#009900">ERLANG_OTP =</font> OTP-20.0.4 + +include erlang.mk</tt></pre> +</div></div> +<p>The next time you run <code>make</code> Erlang.mk will build and use the version you configured.</p> +<p>Note that there has been reports that this functionality is not compatible with the <code>.ONESHELL</code> feature from GNU Make.</p> <h2 id="_continuous_integration">Continuous integration</h2> -<div class="sectionbody"> -<div class="paragraph"><p>Erlang.mk can automatically test your project against -many different Erlang/OTP versions. This functionality -is documented in the <a href="../ci">Continuous integration</a> chapter.</p></div> -</div> -</div> -<div class="sect1"> +<p>Erlang.mk can automatically test your project against many different Erlang/OTP versions. This functionality is documented in the <a href="../ci">Continuous integration</a> chapter.</p> <h2 id="_configuring_kerl">Configuring Kerl</h2> -<div class="sectionbody"> -<div class="paragraph"><p>All of the Kerl variables can be configured directly in the -Makefile. All you need to do is to export them. For example, -to change the installation directory for the Erlang/OTP -versions managed by Kerl, you could add the following to -your Makefile:</p></div> -<div class="listingblock"> -<div class="content"><!-- Generator: GNU source-highlight +<p>All of the Kerl variables can be configured directly in the Makefile. All you need to do is to export them. For example, to change the installation directory for the Erlang/OTP versions managed by Kerl, you could add the following to your Makefile:</p> +<div class="listingblock"><div class="content"><!-- Generator: GNU source-highlight 3.1.8 by Lorenzo Bettini http://www.lorenzobettini.it http://www.gnu.org/software/src-highlite --> -<pre><tt><span style="font-weight: bold"><span style="color: #0000FF">export</span></span> KERL_INSTALL_DIR <span style="color: #990000">=</span> <span style="color: #009900">$(CURDIR)</span>/erlang</tt></pre></div></div> -<div class="paragraph"><p>When configuring paths like this, always make sure to provide -an absolute path in the value. Erlang.mk will NOT expand them -automatically for you.</p></div> -</div> -</div> +<pre><tt><b><font color="#0000FF">export</font></b> KERL_INSTALL_DIR <font color="#990000">=</font> <font color="#009900">$(CURDIR)</font>/erlang</tt></pre> +</div></div> +<p>When configuring paths like this, always make sure to provide an absolute path in the value. Erlang.mk will NOT expand them automatically for you.</p> + |