GLES32 Renderer Implementation Pt. 1 - Integrating Google ANGLE and Preliminary Validation

[CrotAA]

Objective

Introduce a minimal GLES 3.2 backend using Google ANGLE.
The goal is to validate renderer abstraction and build system integration.

This phase does NOT aim to implement full rendering features.
Compilation success is the primary acceptance criteria.

---

Scope

1. Integrate Google ANGLE into the CMake build system
2. Add basic GLES32Renderer implementation
3. Ensure project builds successfully with the new backend

---

Implementation Plan

1. ANGLE Integration

• Add ANGLE as external dependency (submodule or prebuilt)
• Configure CMake include directories and link libraries
• Verify <GLES3/gl3.h> can be included without errors

2. GLES32Renderer Scaffold

• Create GLES32Renderer class inheriting from Renderer
• Implement required virtual methods with placeholder logic
• Add minimal initialization code (e.g., context creation stub)

3. Build Validation

• Confirm successful compilation
• No runtime rendering requirement at this stage

---

Acceptance Criteria

• Project builds successfully with GLES backend enabled
• No unresolved symbols or linker errors
• Backend selectable via configuration flag (if applicable)

---

Notes

This is a structural backend addition to prepare for future cross-platform rendering support.

[ModulePillow]

@CrotAA
Integrating a full OpenGL ES 3.2 backend is a heavy workload😇.
To make the workload simpler, you can focus on fewer things😎:

• Use CMake to integrate ANGLE. This module allows GLES32 APIs to run on Windows.
• Implement any features to be familiar with them. e.g.: ETC2 compression, GLSL compilation, or simple swap-chain creation.

[CrotAA]

Great, that sounds like a solid approach.
I’ll focus first on integrating ANGLE through CMake and ensuring the backend compiles properly.
As an initial validation, I’ll implement GLSL shader compilation and build from there.🥰