Inno.Build.Toolchains.Sdl3
Section titled “Inno.Build.Toolchains.Sdl3”SDL component source declaration and protected native publication for an explicitly frozen target.
Read the linked task or ownership explanation before using the exact API below.
Declare before generating
Section titled “Declare before generating”Sdl3Toolchain.CreateRecipe borrows the context and returns actual source, build implementation, SDK and ordered option inputs without staging, starting tools or reading generated outputs. Fingerprinting still reads real declared content. BuildAsync consumes that declaration and adds the selected binding generation’s actual content before publication.
The SDK provider chooses the target and Shared component options. Shared recipe code does not reselect the host OS or provide a second executable. Use the selected Editor/product or Support Pack plan; those plans have different explicit closures.
Retain the preparation result
Section titled “Retain the preparation result”Keep frozen tools/options/generation protected through the build and dispose NativeBuildProduct after deployment/linking finishes. Source/CMake/output locations follow context.engineRoot, not the assembly location. Cancellation stops process work and is checked before launch/copy. Existing files do not certify current publication, and failed/missing output still fails platform closure validation. See SDL integration and Native preparation.
Host usage
Section titled “Host usage”Supply existing live dependencies. This example checks the host contract; it does not initialize a complete product or certify a physical device.
using System.Threading;using System.Threading.Tasks;using Inno.Build.Toolchains;using Inno.Build.Toolchains.Sdl3;
static Task<NativeBuildProduct> PrepareComponentAsync( NativeBuildContext preparedContext, CancellationToken cancellationToken) { return Sdl3Toolchain.BuildAsync(preparedContext, cancellationToken);}Source boundary
Section titled “Source boundary”The source project defines the selected host declarations. Script projection and platform execution require their separate evidence.
API reference
Section titled “API reference”Types and exact member contracts retain declarations and source XML from the recorded engine capture.