diff options
author | Loïc Hoguin <[email protected]> | 2014-12-20 13:51:05 +0200 |
---|---|---|
committer | Loïc Hoguin <[email protected]> | 2014-12-20 13:51:05 +0200 |
commit | 1cea2ce79b5ec9b671d24f0628fa2b78a95b772c (patch) | |
tree | cc091954c3f0a5bd7101c7d6c078a994522e6ca4 | |
parent | 604b98dfa81ba14f2359e5b2933fef00929890b3 (diff) | |
download | erlang.mk-1cea2ce79b5ec9b671d24f0628fa2b78a95b772c.tar.gz erlang.mk-1cea2ce79b5ec9b671d24f0628fa2b78a95b772c.tar.bz2 erlang.mk-1cea2ce79b5ec9b671d24f0628fa2b78a95b772c.zip |
Add a "Why erlang.mk?" section
-rw-r--r-- | README.md | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -5,6 +5,17 @@ Common Makefile rules for building and testing Erlang applications. Also features support for dependencies and a package index. +Why erlang.mk? +-------------- + +A number of reasons might push someone to use erlang.mk instead of +an Erlang-based build tool, including but not limited to the following: + + * You want a very fast compilation and test cycle + * You want the full power of Unix at your disposal when hooking into your build tool + * You want to use the deps mechanism with non-Erlang Makefile-based projects + * Your project will be part of a larger make or automake based environment + Requirements ------------ |