Bake scripts into files.

Executes @EXEC to the end of the line or @STOP within in any given
file. you also may use @COMPILECMD instead, it has a higher priority
than @EXEC. Newline-only supports backslashes to include additional
lines.

you may see a real example in the primary and only source file: `bake.c'.
this is not targeted toward any language and should be fairly flexible,
especially when multi-line comments are available.

The execution takes place at the root of the target file, so if you have:
/my/test/file.c, and then execution takes place at /my/test.

Buildng

Bootstrapping may be done with Shake, simply run `./shake ./bake.c'

Initial building may be done by examining and running `install.sh',
if you don't want to install it right away, run `SUDO= TARGET=. ./install.sh'

Name/Arg Extension

$@: the name of the executed file
$*: the text of the filename before the last dot
$+: the remaining arguments to Bake

Options Extension

only one option may be in use at a time, and must come as the first argument.

-h, --help: displays help message, similiarly to empty input.
-n, --dry-run: DRYRUN, does NOT run anything!

Shake

Bake was inspired by the Bash-based Shake utility (formerly eMake,
he liked my suggestion for a name), written which you may view at:
<http://bis64wqhh3louusbd45iyj76kmn4rzw5ysawyan5bkxwyzihj67c5lid.onion/anon/shake>

Bake includes Shake, both in installation, and as a bootstrapper. It
is included under authorization of it's creator. It is not a replacement
for Bake, but it is platform independent in regards to its use of Bash.

Shake is limited in comparison to Bake, the first line including @COMPILECMD.
It supports all Name/Arg Extensions, and all options. It does not support
@STOP in any way.

Bake is licensed under the GPLv3, See LICENSE.

Bake began on September 13th, 2023.