Snapshot · Nov 21, 2026

Build and integration

SnBuild owns the renderer’s build graph. Its workspace name is SnAPI.Renderer.New. The public headers use <Renderer/Module/Header.h>. Include the header that owns the contract, and give the consuming SnBuild module an ordinary dependency on the module that implements it. Optional importers and integrations are selected per consumer. A public header’s presence in the reference does not imply that a particular target links its module.

Build the library on Linux

From the renderer workspace root, with compatible SnAPI.Core and SnAPI.Math workspaces next to it:

SnBuild build --Configuration Development --Workspace . \
  --DependencyWorkspace ../SnAPI.Core --DependencyWorkspace ../SnAPI.Math \
  --Platform Linux SnAPI.Renderer.New --Jobs 18

Use SnAPI.Renderer.New.Example in place of the library target to build the ordinary integration example. The supplied reference application has the separate build target SnAPI.Renderer.OpenPBRReference. Repository toolchain and provider options apply to each target.

Choose the backend by capability

RendererConfig controls backend selection and shader compilation policy. Null exercises host contracts without native rendering. Vulkan is the live GPU backend covered by the Linux examples. Check the actual runtime capabilities before composing features that need extension, format, queue, or ray-tracing support. The backend enum names other families as well. Availability is determined by the backend implementation and build.

Which docs should I read?