Build and run development entries
Section titled “Build and run development entries”The repository provides ordinary .NET executable entries for Build and Editor. The SDK compiles their real project references; starting them does not reflectively load a second unpublished copy of the CLI or Editor.
Prepare support or build the Editor
Section titled “Prepare support or build the Editor”Run from the engine checkout with its selected SDK:
dotnet run --project entry/InnoEngine.Build/InnoEngine.Build.csprojdotnet run --project entry/InnoEngine.Build/InnoEngine.Build.csproj -- support --product player --target windows-x64dotnet run --project entry/InnoEngine.Build/InnoEngine.Build.csproj -- editor --configuration ReleaseNo arguments prepares support for the development host’s Editor. Support prepares applicable Native dependencies, bindings and backend tools; it does not compile the whole managed Editor product. The editor command builds the actual Editor entry and its dependencies.
Support/editor/product-clean defaults follow the entry’s build configuration; Support Pack defaults to Release. Explicit configuration and target selection remain caller-owned. A portable target description compiling on a host does not prove that host can execute the target’s Native toolchain.
For script, plugin or Player export, use the corresponding workflow rather than treating support preparation as a completed product build. See build a Player and compile project scripts.
Start the actual Editor product
Section titled “Start the actual Editor product”dotnet run --project entry/InnoEngine.Editor/InnoEngine.Editor.csprojdotnet run --configuration Release --project entry/InnoEngine.Editor/InnoEngine.Editor.csproj -- /absolute/MyGameThe SDK host selects the WindowsX64 or MacOSArm64 product reference. Its composition runs directly on the original main thread. Without a project path, the product opens its native directory chooser; canceling exits normally. Required platform tooling must be available for the first preparation.
Normal builds own their selected reference closure even when an IDE solution excludes a product as a separate root. Design-time evaluation does not trigger Native preparation or introduce another IDE-only output tree. Subsequent source changes use the SDK’s actual dependency graph.
Solution Debug/Release builds the shared source, tools, applicable tests and current host Editor through the entry’s conditional project reference. It does not select every other host or Player product. SourceDebug/SourceRelease validates source without the Editor entry. An unselected product is not built; an unchanged selected output can be incrementally up to date. Portable target-description libraries can compile without executing their target’s Native SDK.
Clean only the selected owner
Section titled “Clean only the selected owner”dotnet run --project entry/InnoEngine.Build/InnoEngine.Build.csproj -- clean --scope product --dry-rundotnet run --project entry/InnoEngine.Build/InnoEngine.Build.csproj -- editor --cleanInspect dry-run before intentional cleanup. Product clean acquires exclusive access to the selected entry/platform product configuration. A running Editor holds a reader lease, preventing deletion of its deployment. Other configurations, Native/Binding caches, Support Packs, game outputs and user data are outside that product scope.
Cache cleanup uses registered owners and their dependency/reader protections. It does not guess ownership of an old unregistered directory. --clean is an editor option, not a general command flag. Do not remove locks to bypass an active consumer.
Publish a macOS development application
Section titled “Publish a macOS development application”On a supported macOS host:
dotnet publish entry/InnoEngine.Editor/InnoEngine.Editor.csproj -c Release -r osx-arm64The platform-owned target creates InnoEngine.Editor.app beside the publish output. Contents/MacOS contains the published application, Contents/Resources contains the licensed logo.icns, and Info.plist identifies io.innoengine.editor and its executable/icon. Normal dotnet run still runs the bare executable.
The default publication is framework-dependent. Add --self-contained true when distributing to machines without the required .NET runtime. This operation does not sign or notarize the application and is not a formal engine release. Windows uses the existing logo.ico through ApplicationIcon; both remain subject to the separate branding license.
Keep preparation outside fast reads
Section titled “Keep preparation outside fast reads”Build tooling once, then invoke its DLL or use --no-build for prepared documentation queries. Query an explicit snapshot; queries do not rebuild an index, discover a sibling checkout, compile the engine or prepare Native dependencies silently.
Entry-owned cancellation removes the Ctrl+C subscription on exit. Exit codes distinguish success, cancellation and unhandled failure; product hosts retain responsibility for sessions, devices, workers and callback retirement. See the entry references for exact ownership boundaries and validation before claiming a product verified.