How libretro/ludo works
Main Components
a. Core Components:
• Libretro Interface Layer (/libretro)
• Core System (/core)
• Video Subsystem (/video)
• Audio Subsystem (/audio)
• Input System (/input)
• Menu System (/menu)
b. Supporting Components:
• State Management (/state)
• Settings Management (/settings)
• Save Systems (/savefiles, /savestates)
• Scanner (/scanner)
• Playlists (/playlists)
• Notifications System (/notifications)
┌─ User Interface Layer ─────────────────┐
• Menu System | Notifications | Input UI │
• Application Layer ───────────────────┐│
• Scanner | Playlists | History ││
• Core Services ─────────────────────┐││
• State | Settings | SaveStates │││
• Media Layer ───────────────────┐ │││
• Video | Audio | Input │ │││
• Libretro Layer ─────────────┐ │ │││
• Core Loading | Core Control │ │ │││
• ┘─┘──┘─┘
Component Relationships
• Libretro Layer ↔ Media Layer (core output/input)
• Media Layer ↔ UI Layer (display/sound/controls)
• Core Services → All Layers (state/settings access)
• Application Layer ↔ UI Layer (user interaction)
Technical Details
Annotations for:
• Go-specific implementations
• Platform-specific components (video_darwin.go vs video_notdarwin.go)
• Core loading mechanisms
• File system interactions
External Dependencies
Connections to:
• OpenGL (>= 2.1)
• OpenAL
• GLFW 3.3
• Libretro cores
The central role of the libretro interface
This architecture reflects a modern gaming frontend with clear separation of concerns and modular design, making it maintainable and extensible.