Kyle Benesch

The libtcod renderers have specific limitations. Converting your renderer to fit with libtcod's contexts will remove many of the features that make your renderer worth using over libtcod's strict single-layer...

You could, but I'm so busy trying to clean up libtcod. For me the best thing you can do is handle any integration yourself and add ports of your libraries...

`doxygengroup` seems to be the ideal directive for the older docs. This lets me group things nicely without needing to change the overall structure.

Breathe directives are causing conflicts, so I'm looking into using Exhale to extract the docs from the sources instead.

So far all docs that were only in the headers are now in the online docs. However it's mostly auto-generated and there are multiple symbols included which should be removed....

Note that the current wheels already include the `py2.py3` tag which makes any extra `cp` and `pp` tags redundant. `py2.py3` is the 'universal' Python tag and is enough to match...

`pyproject.toml` is super nice but I don't think it will resolve your current issues with wheels. What it can do is make it so that cffi is installed *before* the...

This would be an example of a workflow. This script would be stored in a path like `.github/workflows/build-libs.yml` in the repository, and will take affect as soon as it's pushed...

> There is a known issue that will require a recompile of the Windows binaries with [Visual Studio 14+](https://wiki.python.org/moin/WindowsCompilers), and will probably never work for all versions of Python. Apparently,...

> ... and noticed that the automated tests no longer run. Does anyone know why? [If you check the commits on GitHub then TravisCI's last status check was Nov 26,...