New formula: makeheaders

A tiny but powerful utility from the sqlite and fossil folks (it's used by both projects) for more scalable C/C++ codebases (read: cheaper to maintain), in the flavor of source-also-declares-interface--style development, vaguely similar to Go (Golang).  `makeheaders` is the **source** preprocessor that generates headers that makes the magic happen.  Also, it can generate the externally-exported library header too (`-H` instead of `-h`)! 

The github packaging makes it available to everyone that likes versioning / automation, i.e., a package manager and/or configuration management.
> 'sorry, but we don't care'

Nobody is saying this, and labelling *anyone* around here immature doesn't help get anything done, FWIW.

A big part of the problem here is that you're trying to *develop* something using commands primarily intended for *users*. It is advised that to see the full, wrapped output that people do ``` brew install -v xxxxxxx ` which generates:

```
==> Downloading https://github.com/steakknife/makeheaders/archive/1.4-2.tar.gz
Already downloaded: /Library/Caches/Homebrew/makeheaders-1.4-2.tar.gz
==> Verifying makeheaders-1.4-2.tar.gz checksum
tar xf /Library/Caches/Homebrew/makeheaders-1.4-2.tar.gz
==> sh ./bootstrap
configure.ac:5: installing './compile'
configure.ac:2: installing './install-sh'
configure.ac:2: installing './missing'
Makefile.am: installing './depcomp'
==> ./configure --disable-debug --disable-dependency-tracking --disable-silent-rules --prefix=/usr/local/Cellar/makeheaders/1.4-2
configure: WARNING: unrecognized options: --disable-debug
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... clang
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether clang accepts -g... yes
checking for clang option to accept ISO C89... none needed
checking whether clang understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of clang... none
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-debug
==> make install
clang -DPACKAGE_NAME=\"makeheaders\" -DPACKAGE_TARNAME=\"makeheaders\" -DPACKAGE_VERSION=\"1.4\" -DPACKAGE_STRING=\"makeheaders\ 1.4\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"makeheaders\" -DVERSION=\"1.4\" -I.     -g -O2 -c -o makeheaders.o makeheaders.c
clang  -g -O2   -o makeheaders makeheaders.o
make[1]: Nothing to be done for `install-data-am'.
 ./install-sh -c -d '/usr/local/Cellar/makeheaders/1.4-2/bin'
  /usr/bin/install -c makeheaders '/usr/local/Cellar/makeheaders/1.4-2/bin'
==> Cleaning
==> Finishing up
ln -s ../Cellar/makeheaders/1.4-2/bin/makeheaders makeheaders
==> Summary
🍺  /usr/local/Cellar/makeheaders/1.4-2: 5 files, 52K, built in 7 seconds
```

Brew (the executable itself) doesn't particularly *care* (due to being a piece of code) how you structure your releases. The hyphen isn't overly important here. Brew cuts off lines at a certain point and *that* is the reason you're seeing ``` /usr/local/Cellar/makeheaders/2 ```.

If you run ``` brew install -v ``` you **will** see ``` 🍺  /usr/local/Cellar/makeheaders/1.4-2: 5 files, 52K, built in 7 seconds```.