build-vmaf

Build libvmaf with Meson and Ninja across cpu, cuda, sycl, and hip backends.

3|1|Updated May 28, 2026
One-click install
npx skills add https://github.com/VMAFx/vmafx --skill build-vmaf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-vmaf
Source: https://github.com/VMAFx/vmafx/tree/main/.claude/skills/build-vmaf
Command: npx skills add https://github.com/VMAFx/vmafx --skill build-vmaf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from building the libvmaf library and CLI by turning backend selection, build configuration, and sanitizer setup into a consistent, repeatable workflow.

Core Features & Use Cases

  • Backend-aware builds: Handles cpu, cuda, sycl, hip, and all-target builds with the correct Meson flags and availability checks.
  • Build-type control: Supports debug, release, and relwithdebinfo configurations while enforcing sensible defaults.
  • Sanitizer support: Configures address, undefined, and thread sanitizers with validation for incompatible combinations.
  • Output reporting: Reports elapsed build time and the resulting CLI and shared library artifact paths.
  • Use case: A developer can quickly produce a clean GPU-enabled build for testing, then switch to a release CPU build for packaging without remembering the exact command sequence.

Quick Start

Ask the skill to build libvmaf with the desired backend, build type, and sanitizer settings, and it will run the correct Meson and Ninja commands for you.

Frequently Asked Questions about build-vmaf

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

FAQPage Schema
How do I build libvmaf with a CUDA or HIP backend for GPU acceleration?

To build libvmaf with a GPU backend, the Skill configures Meson and Ninja with the correct flags for cuda, sycl, or hip, validating toolchain availability to produce the expected artifacts.

What Meson and Ninja commands are needed to compile the libvmaf CLI?

Compiling the libvmaf CLI requires running Meson and Ninja commands with validated backend, build type, and sanitizer settings, which the Skill executes automatically to report artifact paths and elapsed time.

Can I enable address or thread sanitizers when building libvmaf?

Yes, libvmaf builds support address, undefined, and thread sanitizers, validating incompatible combinations to ensure a correct debug or relwithdebinfo build configuration.

Do I need specific compiler toolchains to build libvmaf for local development?

Local development builds require Meson, Ninja, and the appropriate compiler toolchains for your chosen backend, ensuring reproducible builds across cpu, cuda, sycl, and hip configurations.

What is the best way to switch between a release CPU build and a debug GPU build of libvmaf?

The best way is to specify the desired backend and build type, letting the Skill apply the correct Meson flags to seamlessly switch between release CPU packaging and debug GPU testing.