raylib

The core category contains 49 examples demonstrating the fundamental functionality of the raylib rcore.c module. These examples cover essential platform features including:

• Window Management: Window creation, flags, letterboxing, and HighDPI support.
• Input Handling: Keyboard, mouse (including wheel), gamepad, multitouch, gestures, and virtual controls.
• Camera Systems: 2D cameras (including zoom and split-screen) and 3D cameras (free, first-person, FPS, and split-screen).
• System & Platform: Delta time, monitor detection, custom logging, file/directory handling, clipboard text, and screen recording.
• Rendering & Math: Scissor testing, render textures, viewport scaling, random values, and compute hashes.
• Game Logic Patterns: Screen managers, undo/redo systems, and input action mapping.

rexm is a command-line tool designed to automate the management of the raylib examples collection. It handles the complex process of adding, renaming, removing, validating, and building examples across multiple platforms (Desktop and Web) and build systems (Makefiles, Visual Studio, and raylib.com web assets).

Use rexm to ensure your new or modified examples follow the required metadata structure, include necessary resources, and are correctly registered in all raylib build configurations and documentation.

rexm help

The rlparser tool scans C header files (specifically raylib.h) to extract metadata about defines, structs, enums, and functions. The extracted data is organized into the following structures:

• struct DefineInfo
• struct FunctionInfo
• struct StructInfo
• struct EnumInfo

This tool is useful for generating documentation or metadata files in formats like JSON, XML, or LUA from the raw C header source.

raylib is a C programming library designed for graphics/multimedia applications. It is considered a graphics library with high-level features rather than a full game engine.

Unlike engines like Unity, Unreal, or Godot, raylib does not provide:

• A Screen manager
• A GameObject/Entity manager
• A Resource Manager

It provides full control at a low level, allowing users to build applications in a 'handmade' way without the abstraction of a GUI editor or complex integrated tools.

While rlparser can work with other C headers, they must follow specific structural patterns to be parsed correctly:

Functions

Must be on a single line with this structure: <retType> <name>(<paramType[0]> <paramName[0]>, <paramType[1]> <paramName[1]>); <desc> Warning: Breaking functions into multiple lines will break the parsing process.

Structures

Must follow this multi-line format:

<desc>
typedef struct <name> {
    <fieldType[0]> <fieldName[0]>; <fieldDesc[0]>
    <fieldType[1]> <fieldName[1]>; <fieldDesc[1]>
} <name>;

Enums

Must follow this multi-line format:

<desc>
typedef enum {
    <valueName[0]> = <valueInteger[0]>, <valueDesc[0]>
    <valueName[1]>, 
    <valueName[2]>, <valueDesc[2]>
} <name>;

Enum Rules:

• If a value is not provided, it is assigned as (<previous_value> + 1).
• Value descriptions are optional.

raylib uses a modified version of GLFW to ensure compatibility across different platforms. The primary modification involves renaming specific static functions that share names across different platforms, allowing all GLFW source files to be combined into a single file (typically rglfw.c). Additionally, the 'Null' platform is disabled as it is not required by raylib.

If you are inspecting the source or debugging platform-specific behavior, note that the following functions have been renamed from their original GLFW names to avoid collisions:

/* Renamed functions in the raylib GLFW modification: */
- createKeyTables()
- translateKey()
- acquireMonitor()
- releaseMonitor()

To use this template with GNOME Builder, you can either:

• Click directly on the meson.build file within the application.
• Open GNOME Builder first, then click the open button at the top-left and select the project directory.