added reasons to use
This commit is contained in:
parent
d1fba033b6
commit
bcc4dd3401
1 changed files with 17 additions and 0 deletions
17
README.md
17
README.md
|
@ -31,6 +31,23 @@ command line (see *Usage* section of this README). Objects will be placed in the
|
||||||
directory `BUILD_DIR/obj/`, and the `TARGET` will be placed at
|
directory `BUILD_DIR/obj/`, and the `TARGET` will be placed at
|
||||||
`BUILD_DIR/$(TARGET)`.
|
`BUILD_DIR/$(TARGET)`.
|
||||||
|
|
||||||
|
## Why use this tool?
|
||||||
|
|
||||||
|
`mgen` offers distinct advantages over other, more complex build systems. These
|
||||||
|
include:
|
||||||
|
|
||||||
|
1. **Simplicity.** There are no special languages to learn, extra configuration
|
||||||
|
files, and countless features that you won't ever use. Of course, if you need
|
||||||
|
those things, there are other options available; that is not the space `mgen`
|
||||||
|
intends to occupy.
|
||||||
|
1. **Extensibility.** Because `mgen` adds to your existing makefile, you can
|
||||||
|
write your own build rules in a language you already know: make. Your custom
|
||||||
|
rules can use the ones generated by `mgen`, or you can just use the generated
|
||||||
|
ones; it's up to you, `mgen` gives you that option.
|
||||||
|
1. **Portability.** Once the makefile is generated, it can be run on any machine
|
||||||
|
that runs `make`. Your users do not have to have `mgen` to compile your
|
||||||
|
program, they can just use the generated makefile.
|
||||||
|
|
||||||
## Usage
|
## Usage
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
Loading…
Reference in a new issue