Development build c61897db

Built from c61897db - docs: Azahar's internal resolution is offered; its states carry the renderer's surfaces (#223)

Since 0e8f706:

• docs: Azahar's internal resolution is offered; its states carry the renderer's surfaces (#223) (c61897d)

what	file
Windows x64	chimera-win-x64-c61897db.zip
Linux x64	chimera-linux-x64-c61897db.tar.gz

Both carry the frontend and its natives. They carry no cores, and
Chimera downloads none: get a core's .chimeraCore package from the
project that builds it and put it in the Cores folder beside Chimera.
BUILD.txt names the exact commit this was built from and
LICENSES.md states its terms.

Each core brings its own licence with it, and some (Genesis Plus GX,
Opera, Snes9x) forbid commercial use - which binds whatever they are
installed into. Chimera shows a core's terms once it is in the folder.

Windows will warn that the executable is unsigned and from an unknown
publisher; it is not signed, and there is no way around that warning
short of buying a certificate.

Not for submissions. A development build is replaced on every
change, so it may stop being downloadable - which means a movie made
on it can stop being replayable. Do not use a dev build to
produce a TAS for submission to toolAssisted.run; use a
nightly,
which is dated and kept forever.