build-linux-binary

Automates multi-architecture Linux builds and packaging for XerahS.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds Linux binaries and packages for XerahS, reducing manual packaging toil and ensuring consistent artifacts across platforms.

Core Features & Use Cases

  • Automates multi-architecture builds (x64 and ARM64) and creates both deb and rpm packages in dist/.
  • Handles common build blockers such as file locking and stale processes during Linux packaging.
  • Prevents Avalonia XAML precompilation failures by addressing namespace-related converter issues during the build.

Quick Start

Run the packaging script to generate Linux packages for both x64 and arm64 architectures.

Frequently Asked Questions about build-linux-binary

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

FAQPage Schema
How do I automate Linux builds and packaging for .NET applications?

Automating Linux builds and packaging handles multi-architecture compilation to generate deb and rpm artifacts. It reduces manual toil by streamlining the build process into a single workflow for x64 and arm64 architectures.

Why does Avalonia XAML precompilation fail during Linux packaging?

Avalonia XAML precompilation fails during Linux packaging due to namespace-related converter issues. The build process addresses these specific namespace conflicts to prevent precompilation failures and ensure successful binary generation.

How do I create both deb and rpm packages for x64 and arm64 architectures?

Create deb and rpm packages for x64 and arm64 architectures by running an automated build script that targets both architectures. The process outputs the finalized packages directly to the dist directory for artifact verification.

What causes file locking and stale processes when building Linux binaries?

File locking and stale processes during Linux binary builds occur when previous packaging attempts leave active processes or locked files. The build workflow handles these blockers by clearing stale processes before continuing compilation.

Does this Linux build workflow handle post-build validation for recent outputs?

The Linux build workflow handles post-build validation by verifying artifacts in the dist directory. It checks for recent outputs to confirm that the deb and rpm packages were successfully generated for both x64 and arm64 architectures.