radius-build-cli

Builds the Radius CLI binary from source using Makefile targets with optional debug and version injection.

1.7k|136|Updated Feb 20, 2021
One-click install
npx skills add https://github.com/radius-project/radius --skill radius-build-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: radius-build-cli
Source: https://github.com/radius-project/radius/tree/main/.github/skills/radius-build-cli
Command: npx skills add https://github.com/radius-project/radius --skill radius-build-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds the Radius CLI binary from source, enabling reproducible local builds and cross-platform deployment.

Core Features & Use Cases

  • Build the Radius CLI from source using the project's Makefile targets (build-rad, build-rad-<os>-<arch>), producing binaries under dist/.
  • Create release or debug builds with optional DEBUG=1, and inject version metadata via linker flags for traceability.
  • Validate builds by executing and verifying the binary version output to ensure correctness across platforms.

Quick Start

Build the Radius CLI for the current platform using the default Makefile target.

Frequently Asked Questions about radius-build-cli

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

FAQPage Schema
How do I build the Radius CLI from source for local development?

Build the Radius CLI from source for local development by running the default Makefile target build-rad, which compiles the Go binary and outputs the executable to the dist directory.

Can I cross-compile the Radius CLI for Linux, macOS, and Windows?

Cross-compile the Radius CLI across Linux, macOS, and Windows by invoking platform-specific Makefile targets using the build-rad-<os>-<arch> naming convention, generating binaries for each target operating system and architecture.

How do I create a debug build of the Radius CLI?

Create a debug build of the Radius CLI by setting the DEBUG=1 environment variable when running the make command. This configures the build process to include debugging symbols and disable optimizations.

How does the Radius CLI build process inject version metadata?

The Radius CLI build process injects version metadata via Go linker flags during compilation. This ensures traceability by embedding version information directly into the binary for verification through version output.

What is the best way to verify a Radius CLI build after compilation?

Verify a Radius CLI build after compilation by executing the generated binary from the dist directory and checking its version output. This validates that the build completed successfully and the version injection worked correctly.

Do I need Make to compile the Radius CLI binary?

You need Make to compile the Radius CLI binary because the build process relies on predefined Makefile targets like build-rad and build-rad-<os>-<arch> to automate the Go compilation and cross-compilation steps.