How travisvroman/kohi works
Project Type and Purpose
• The project is a game engine built from scratch using C with Vulkan for rendering. It also supports plugins (for audio using OpenAL, standard UI, etc.) and is structured as a modular engine with multiple shared libraries.
• The README makes it clear that this engine is both a learning resource (with tutorial and live stream aspects) and a basis for game development. The engine is built around clear separation between the core functionalities and plugin extensions.
Analyzing the File Structure
• There are several top-level directories each representing a component of the engine:
• kohi.core: Contains low-level, shared functionalities such as math libraries, containers, string utilities, memory management, and the platform layer.
• kohi.runtime: Contains the core engine logic and systems (renderer, audio, input, asset handling, scene management, etc.).
• Plugins (subdirectories starting with “kohi.plugin.”):
▪ kohi.plugin.audio.openal – the audio backend using OpenAL.
▪ kohi.plugin.renderer.vulkan – the Vulkan-based renderer plugin.
▪ kohi.plugin.ui.standard – the retained-mode UI plugin with controls.
▪ kohi.plugin.utils – utility plugin components.
• Application and Testbed Components:
▪ testbed.kapp – The main application consuming the engine, configuring plugins and libraries.
▪ testbed.klib – Contains game-specific functionalities and code (hot reloadable).
▪ Additional test components under kohi.core.tests.
• Tools:
▪ kohi.tools.versiongen and kohi.tools – command-line and utility tools used by the engine (e.g., version generation).
• Build and configuration scripts (Makefiles, build scripts for Windows/Linux/macOS) and configuration files give cues about the build environments and dependencies.