Engine

Engine Codebase Structure

An overview of the Nevo Engine internal directory layout and key folders.

Directory Overview

The Nevo Engine codebase is organized into several key directories, each serving a specific purpose in the engine's architecture. This document details the structure for engine developers.

include/

Contains public and internal header files for the engine.

  • internals/: Core engine systems, resource management, and internal ECS logic.
  • Eigen/, imgui/, GL/, etc.: Third-party libraries integrated into the engine.

src/

Implementation files for the engine's core functionality.

  • internals/: Implementation of internal systems.
  • platform/: Platform-specific code (e.g., OpenGL implementation for Linux).
  • rendering/: Rendering pipeline and shader management.
  • scripting/: Implementation of scripting systems.

shared/

Code and headers shared across different parts of the engine and potentially with external modules/games.

  • ECS/: The core Entity Component System data structures and managers.
  • input/: Input handling abstractions.
  • debug/: Debugging utilities and Tracy integration.

dependencies/

External dependencies managed within the repository (e.g., Tracy profiler).

build/ & buildtmp/

Generated by the build system (CMake). Contains compiled binaries and intermediate build artifacts.

conductor/

Management files for the Conductor spec-driven development framework.