build-windows-exe

Build x64 and ARM64 Inno Setup installers for XerahS.

309|15|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/ShareX/XerahS --skill build-windows-exe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-windows-exe
Source: https://github.com/ShareX/XerahS/tree/main/.ai/skills/build-windows-exe
Command: npx skills add https://github.com/ShareX/XerahS --skill build-windows-exe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds Windows executables (x64 and ARM64) for XerahS using a packaging script, addressing common file-lock issues during compilation and ensuring reliable Inno Setup installers.

Core Features & Use Cases

  • Sequentially builds x64 and ARM64 architectures with Inno Setup installers.
  • Performs pre-build cleanup and process termination to avoid file locks.
  • Validates that artifacts exist in the dist folder after a successful run.

Quick Start

Run the build script for Windows from the repository root and verify the installers appear in dist.

Frequently Asked Questions about build-windows-exe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Windows installer builds for multiple architectures?

Automate Windows installer builds by sequentially processing x64 and ARM64 architectures to compile, package, and generate Inno Setup installers. This approach runs single-threaded MSBuild tasks to ensure reliable packaging and validate artifacts in the dist folder.

Why does MSBuild fail with file lock errors during packaging?

MSBuild packaging fails with file lock errors when processes retain handles to output artifacts. Resolve this by performing pre-build cleanup and terminating lingering processes before compilation to clear file locks and ensure a successful Windows build.

Does Inno Setup support building x64 and ARM64 installers in CI workflows?

Yes, Inno Setup supports building x64 and ARM64 installers in CI workflows. The process sequentially compiles target architectures and validates that the generated installers exist in the dist directory before completing the release run.

What is the best way to validate Windows build artifacts after compilation?

Validate Windows build artifacts after compilation by checking the dist folder for the expected installer outputs. Artifact validation confirms that the single-threaded MSBuild run successfully packaged the x64 and ARM64 executables before release.

How to handle cleanup before a Windows release build to avoid locked files?

Handle cleanup before a Windows release build by terminating active processes and clearing previous artifacts. This pre-build cleanup clears file locks, allowing the single-threaded MSBuild packaging script to generate Inno Setup installers without interruption.