Use abstraction instead of using SDL dependencies.

Use CMake definitions to specify config paths and filenames.

Fix CMake lib dependencies for crypto/SSL. Also ensure websockets work on macOS for both client and server.

Come up with our own logging system.

Tidy up CMake.

Also provide abstraction to fopen_s only available to Windows.

Include _s wrappers for most standard function calls.

Implement gamepad logic for macOS.

Add compatibility for macOS and *NIX files

TODO: inspect building of dependencies

Instead of using macros, use iterators built-in on each list for
filtering and traversing.

Provide support for XInput mappings.

Demonstrate on-the-fly flip for sprites.

Make distinctions between internal and external (downloaded from
third-party servers).

The sprites are now loaded using a utility function in IZ_video.

The magazines for each weapon except the rifles have been drawn.

Add templates for config item types.

Also updated server's config to use the global config module.

Remove symlinks and make codebase use common modules instead.

Rename files in order to prepare for extraction for publishing
subsystems independently.

Make sure to have help messages for both the game and the server.

This file is unnecessary.

Put input and video subsystems into their own directories.

Split the network events to the net directory to keep the app code
implementation clean.

Database will be used for authentication.

Implement the sending of input events to the websocket server.

Update identifiers to be consistent.

Add subdirectories for grouping net-related functions.

Make server optionally have a mountpoint for putting assets.

Connect client to server, save connection details.

Attempt to connect client to server.

Isolate network logic to each subsystem.

Split callback logic into several functions.

Update initialization method.

Use ring example.

Use minimal server echo example instead.

Add libwebsockets client to game executable.

Protocol retrieved from lws git repo for samples.

Websockets server is for game networking.

Add tests for initialization and teardown for all input methods.

Add memory and data-related implementations for handling game data.

Properly mock video function dependencies.

Update input tests.

The game now uses MIDI support for alternative input methods.

Put I/O values to their respective structs.

Isolate input items into their own directory.

Add spine-runtimes to dependencies

Add geometry methods for point, vector, and rectangle.

Ensure one type of test can only be handled at a time.

Implement tests for joystick axis, hat, and button events.

Order files from order of includes.

Add third-party mocks, specify mock files.

/? Do we need first-party mocks in their own files, or can we provide a
mock flag in the implementation files already?

Make device handling opt-in.