Skip to content
Project referenceDevelopmentEngine ccf7d03f
Authored
  • Standard Native component closures and deployment manifests without SDK selection.

Standard Native component closures and deployment manifests without SDK selection.

Start with distribution composition and Support Pack preparation.

StandardNativeComponents constructs Player, Editor and offline Shader-tool plans from explicit graphics profiles, component options and layout functions. CreateStaticPlayer receives explicit static configuration and layout. StandardSupportPackRequirements derives the actual link closure; StandardNativeDeployment encodes a validated Native loading manifest.

The library does not choose a platform, discover SDKs or run Native compilation. Start with build distribution composition, then use the selected contribution’s execution protocol.

Layout callbacks consume relative outputs while constructing deployment descriptions. They must not capture live plugin-generation or domain objects. The calling composition preflights host/toolchain/generator/source inputs. Unavailable capability, cancellation or execution failure cannot publish a partial result. These are host build contracts, not script exports.

Supply existing live dependencies. This example checks the host contract; it does not initialize a complete product or certify a physical device.

using System;
using Inno.Build.Products.Standard;
using Inno.Build.Toolchains;
using Inno.Build.Toolchains.Bgfx;
static ProductNativeBuildPlan ComposePlayer(
BgfxNativeBuildProfile graphics,
Func<string, NativeComponentBuildOptions> options,
Func<string, string, string, string?> layout
) => StandardNativeComponents.CreatePlayer(graphics, options, layout);

The source project defines the selected host declarations. Script projection and platform execution require their separate evidence.

Browse types and members.

Project: Inno.Build.Products.Standard
Source: build/products/Inno.Build.Products.Standard/Inno.Build.Products.Standard.csproj

Type API Description
StandardNativeComponents engine Declares the standard product closures while keeping backend selection out of shared build mechanisms.
StandardNativeDeployment engine Composes validated standard product deployment metadata.
StandardSupportPackRequirements engine Composes validated standard product Support Pack requirements.