API Reference
Overview of the public gp*() macro API, the naming conventions, and how to include the build tool in a project.
Overview of the public gp*() macro API, the naming conventions, and how to include the build tool in a project.
How to set up the root CMakeLists.txt, apply default policies, and start and end the build tool session.
How to add preprocessor definitions to a target with controlled visibility.
How to add compiler flags to a target with controlled visibility, on top of the flags GPBT applies automatically.
All GPBT_* cache variables and options, their defaults, and their effects on the build.
How to express dependencies between modules and thirdparty packages using GPBT's four-level visibility system.
Options that apply only to executable targets, including GUI mode, custom entry points, and resource files.
An overview of all capabilities built into the GP Build Tool.
The CMake meta-build system for Graphical Playground projects. Wraps CMake with a structured, platform-aware API designed for AAA game engine development.
How GPBT manages include paths automatically from the directory layout and how visibility controls which headers are exposed to dependents.
How to add linker flags to a target with controlled visibility.
Additional per-target options including header-only targets, precompiled headers, strict warning control, static and shared linking, and test infrastructure.
How gpBuildToolAutoScan discovers CMakeLists.txt files and registers targets and packages.
How GPBT discovers source files automatically from the directory layout, and how to add or exclude files explicitly.
How to declare modules, executables, and plugins using the GPBT target API.
Per-target test infrastructure, supported test frameworks, and CTest integration.
How GPBT resolves thirdparty dependencies using system packages, prebuilt binaries, and source builds, with platform and compiler awareness built in.