diff options
Diffstat (limited to 'guide/getting_started.html')
| -rw-r--r-- | guide/getting_started.html | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/guide/getting_started.html b/guide/getting_started.html index b3a9d7f..edf340c 100644 --- a/guide/getting_started.html +++ b/guide/getting_started.html @@ -61,7 +61,8 @@ cp .erlang.mk.build/erlang.mk ./erlang.mk rm -rf .erlang.mk.build</pre><p>This is Erlang.mk bootstrapping itself. Indeed, the file you initially downloaded contains nothing more than the code needed to bootstrap. This operation is done only once. Consult the -<a class="ulink" href="updating.asciidoc" target="_top">Updating Erlang.mk</a> chapter for more +<a class="link" href="updating.html" title="Chapter 4. Updating Erlang.mk">Updating Erlang.mk</a> +<a class="xref" href="updating.html" title="Chapter 4. Updating Erlang.mk">Chapter 4, <em>Updating Erlang.mk</em></a> chapter for more information.</p><p>Of course, the generated project can now be compiled:</p><pre class="programlisting">$ make</pre><p>Cheers!</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_getting_started_with_otp_libraries"></a>2.4. Getting started with OTP libraries</h2></div></div></div><p>An OTP library is an Erlang application that has no supervision tree. In other words, it is nothing but modules.</p><p>This kind of project can also be generated by Erlang.mk, using the <code class="literal">bootstrap-lib</code> target:</p><pre class="programlisting">$ make -f erlang.mk bootstrap-lib</pre><p>Erlang.mk will once again bootstrap itself and generate all @@ -73,7 +74,8 @@ You can use the <code class="literal">bootstrap-rel</code> target for this purpo create a project that will build a release:</p><pre class="programlisting">$ make -f erlang.mk bootstrap-lib bootstrap-rel</pre><p>It is often very useful to keep the top-level project for commands useful during operations, and put the components of the system in separate applications that you will then -depend on. Consult the <a class="ulink" href="deps.asciidoc" target="_top">Packages and dependencies</a> +depend on. Consult the <a class="link" href="deps.html" title="Chapter 7. Packages and dependencies">Packages and dependencies</a> +<a class="xref" href="deps.html" title="Chapter 7. Packages and dependencies">Chapter 7, <em>Packages and dependencies</em></a> chapter for more information.</p><p>When you run <code class="literal">make</code> from now on, Erlang.mk will compile your project and build the release:</p><pre class="programlisting">$ make APP hello_joe.app.src @@ -89,7 +91,8 @@ project and build the release:</p><pre class="programlisting">$ make ===> release successfully created!</pre><p>The first time you run this command, Erlang.mk will download <span class="emphasis"><em>relx</em></span>, the release building tool. So don’t worry if you see more output than above.</p><p>If building the release is slow, no need to upgrade your -hardware just yet. Just consult the <a class="ulink" href="relx.asciidoc" target="_top">Releases</a> +hardware just yet. Just consult the <a class="link" href="relx.html" title="Chapter 9. Releases">Releases</a> +<a class="xref" href="relx.html" title="Chapter 9. Releases">Chapter 9, <em>Releases</em></a> chapter for various tips to speed up build time during development.</p><p>You can start the release using the <span class="emphasis"><em>./_rel/hello_joe_release/bin/hello_joe_release</em></span> script, or simply run <code class="literal">make run</code>. The latter will also compile |