clarified GNU make is necessary
This commit is contained in:
parent
5582eac14f
commit
3c990e2ac7
2 changed files with 3 additions and 4 deletions
|
@ -6,8 +6,8 @@ Makefile generator for C projects.
|
|||
|
||||
`mgen` automatically generates build rules for all source files (extension `.c`)
|
||||
it finds in a recursive search of the directory in which it is run. It places
|
||||
the rules in your existing makefile, meaning you can easily change build options
|
||||
and even write your own rules based on those generated.
|
||||
the rules in your existing GNU makefile, meaning you can easily change build
|
||||
options and even write your own rules based on those generated.
|
||||
|
||||
`mgen` will place the generated rules between the strings "`#=mgen_start=#`" and
|
||||
"`#=mgen_end=#`" in your makefile. If these lines are not present, it will add
|
||||
|
@ -49,7 +49,7 @@ include:
|
|||
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
|
||||
that runs GNU `make`. Your users do not have to have `mgen` to compile your
|
||||
program, they can just use the generated makefile.
|
||||
|
||||
## Usage
|
||||
|
|
|
@ -1,5 +1,4 @@
|
|||
use std::{fs, io::ErrorKind};
|
||||
|
||||
use regex::Regex;
|
||||
|
||||
const START_KEY: &str = "#=mgen_start=#\n";
|
||||
|
|
Loading…
Reference in a new issue