diff options
Diffstat (limited to 'docs/en/erlang.mk/1/guide/why/index.html')
| -rw-r--r-- | docs/en/erlang.mk/1/guide/why/index.html | 92 |
1 files changed, 18 insertions, 74 deletions
diff --git a/docs/en/erlang.mk/1/guide/why/index.html b/docs/en/erlang.mk/1/guide/why/index.html index a18ba0d2..659a4a99 100644 --- a/docs/en/erlang.mk/1/guide/why/index.html +++ b/docs/en/erlang.mk/1/guide/why/index.html @@ -62,86 +62,30 @@ <h1 class="lined-header"><span>Why Erlang.mk</span></h1> -<div class="paragraph"><p>Why would you choose Erlang.mk, if not for its -<a href="../overview">many features</a>? This chapter will -attempt to answer that.</p></div> -<div class="sect1"> +<p>Why would you choose Erlang.mk, if not for its <a href="../overview">many features</a>? This chapter will attempt to answer that.</p> <h2 id="_erlang_mk_is_fast">Erlang.mk is fast</h2> -<div class="sectionbody"> -<div class="paragraph"><p>Erlang.mk is as fast as it gets.</p></div> -<div class="paragraph"><p>Erlang.mk will group the compilation of files so as to avoid -running the BEAM more than necessary. This saves many seconds -compared to traditional Makefiles, even on small projects.</p></div> -<div class="paragraph"><p>Erlang.mk will not try to be too smart. It provides a simple -solution that works for most people, and gives additional -options for projects that run into edge cases, often in the -form of extra variables or rules to be defined.</p></div> -</div> -</div> -<div class="sect1"> +<p>Erlang.mk is as fast as it gets.</p> +<p>Erlang.mk will group the compilation of files so as to avoid running the BEAM more than necessary. This saves many seconds compared to traditional Makefiles, even on small projects.</p> +<p>Erlang.mk will not try to be too smart. It provides a simple solution that works for most people, and gives additional options for projects that run into edge cases, often in the form of extra variables or rules to be defined.</p> <h2 id="_erlang_mk_gives_you_the_full_power_of_unix">Erlang.mk gives you the full power of Unix</h2> -<div class="sectionbody"> -<div class="paragraph"><p>Erlang.mk is a Makefile.</p></div> -<div class="paragraph"><p>You could use Erlang.mk directly without configuring anything -and it would just work. But you can also extend it greatly -either through configuration or hooks, and you can of course -add your own rules to the Makefile.</p></div> -<div class="paragraph"><p>In all cases: for configuration, hooks or custom rules, you -have all the power of Unix at your disposal, and can call -any utility <em>or even any language interpreter</em> you want, -every time you need to. Erlang.mk also allows you to write -scripts in this small language called Erlang directly inside -your Makefile if you ever need to…</p></div> -</div> -</div> -<div class="sect1"> +<p>Erlang.mk is a Makefile.</p> +<p>You could use Erlang.mk directly without configuring anything and it would just work. But you can also extend it greatly either through configuration or hooks, and you can of course add your own rules to the Makefile.</p> +<p>In all cases: for configuration, hooks or custom rules, you have all the power of Unix at your disposal, and can call any utility <em>or even any language interpreter</em> you want, every time you need to. Erlang.mk also allows you to write scripts in this small language called Erlang directly inside your Makefile if you ever need to...</p> <h2 id="_erlang_mk_is_a_text_file">Erlang.mk is a text file</h2> -<div class="sectionbody"> -<div class="paragraph"><p>Erlang.mk is a Makefile.</p></div> -<div class="paragraph"><p>Which means Erlang.mk is a simple text file. You can edit a -text file. Nothing stops you. If you run into any bug, or -behavior that does not suit you, you can just open the -<em>erlang.mk</em> file in your favorite editor, fix and/or comment -a few lines, save, and try again. It’s as simple as it gets.</p></div> -<div class="paragraph"><p>Currently using a binary build tool? Good luck with that.</p></div> -</div> -</div> -<div class="sect1"> +<p>Erlang.mk is a Makefile.</p> +<p>Which means Erlang.mk is a simple text file. You can edit a text file. Nothing stops you. If you run into any bug, or behavior that does not suit you, you can just open the <em>erlang.mk</em> file in your favorite editor, fix and/or comment a few lines, save, and try again. It's as simple as it gets.</p> +<p>Currently using a binary build tool? Good luck with that.</p> <h2 id="_erlang_mk_can_manage_erlang_itself">Erlang.mk can manage Erlang itself</h2> -<div class="sectionbody"> -<div class="paragraph"><p>Erlang.mk isn’t written in Erlang.</p></div> -<div class="paragraph"><p>That’s not a good thing, you say? Well, here’s one thing -that Erlang.mk and Makefiles can do for you that Erlang -build tool can’t easily: choose what version of Erlang is -to be used for compiling the project.</p></div> -<div class="paragraph"><p>This really is a one-liner in Erlang.mk (a few more lines -if you also let it download and build Erlang directly) -and allows for even greater things, like testing your -project across all supported Erlang versions in one small -command: <code>make -k ci</code>.</p></div> -</div> -</div> -<div class="sect1"> +<p>Erlang.mk isn't written in Erlang.</p> +<p>That's not a good thing, you say? Well, here's one thing that Erlang.mk and Makefiles can do for you that Erlang build tool can't easily: choose what version of Erlang is to be used for compiling the project.</p> +<p>This really is a one-liner in Erlang.mk (a few more lines if you also let it download and build Erlang directly) and allows for even greater things, like testing your project across all supported Erlang versions in one small command: <code>make -k ci</code>.</p> <h2 id="_erlang_mk_can_do_more_than_erlang">Erlang.mk can do more than Erlang</h2> -<div class="sectionbody"> -<div class="paragraph"><p>Erlang.mk doesn’t care what your dependencies are written in.</p></div> -<div class="paragraph"><p>Erlang.mk will happily compile any dependency, as long as -they come with a Makefile. The dependency can be written -in C, C++ or even Javascript… Who cares, really? If you -need Erlang.mk to fetch it, then Erlang.mk will fetch it -and compile it as needed.</p></div> -</div> -</div> -<div class="sect1"> +<p>Erlang.mk doesn't care what your dependencies are written in.</p> +<p>Erlang.mk will happily compile any dependency, as long as they come with a Makefile. The dependency can be written in C, C++ or even Javascript... Who cares, really? If you need Erlang.mk to fetch it, then Erlang.mk will fetch it and compile it as needed.</p> <h2 id="_erlang_mk_integrates_nicely_in_make_and_automake_projects">Erlang.mk integrates nicely in Make and Automake projects</h2> -<div class="sectionbody"> -<div class="paragraph"><p>If you are planning to put your project in the middle of -a Make or Automake-based build environment, then the most -logical thing to do is to use a Makefile.</p></div> -<div class="paragraph"><p>Erlang.mk will happily sit in such an environment and behave -as you expect it to.</p></div> -</div> -</div> +<p>If you are planning to put your project in the middle of a Make or Automake-based build environment, then the most logical thing to do is to use a Makefile.</p> +<p>Erlang.mk will happily sit in such an environment and behave as you expect it to.</p> + |