cross-platform-builds

Automate cross-platform JUCE plugin builds with CMake and CI/CD.

9|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/yebot/rad-cc-plugins --skill cross-platform-builds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-platform-builds
Source: https://github.com/yebot/rad-cc-plugins/tree/main/plugins/juce-dev-team/skills/cross-platform-builds
Command: npx skills add https://github.com/yebot/rad-cc-plugins --skill cross-platform-builds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive guide to building JUCE plugins across macOS, Windows, and Linux, including CMake configuration, code signing/notarization, and CI/CD pipelines for reproducible builds.

Core Features & Use Cases

  • CMake Configuration: Unified root CMakeLists for all targets and formats
  • Platform-specific Guidance: macOS, Windows, Linux build nuances
  • Code Signing & Notarization: Instructions to sign on macOS and distribute securely
  • CI/CD Integration: Example workflows to automate builds and tests
  • Reproducible Builds: Ensures consistent artifacts across environments

Quick Start

Configure your root CMakeLists to target VST3/AU/AAX on macOS and Windows, then enable CI pipelines to automatically build and test on each PR.

Frequently Asked Questions about cross-platform-builds

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

FAQPage Schema
How do I build JUCE plugins for multiple platforms with CMake?

Cross-platform JUCE plugin builds with CMake use a unified root CMakeLists configuration to target VST3, AU, and AAX formats across macOS, Windows, and Linux. This Skill covers platform-specific build flags, JUCE module linking, and reproducible artifact generation for each target.

Can I automate JUCE plugin builds and code signing in CI/CD pipelines?

Yes. This Skill provides CI/CD integration patterns to automate cross-platform builds, macOS code signing and notarization, and packaging workflows. Automated pipelines ensure consistent, reproducible artifacts on every PR and release.

What's the process for code signing and notarizing JUCE plugins on macOS?

Code signing and notarization on macOS involves obtaining developer certificates, signing plugin binaries with codesign, submitting to Apple's notarization service, and stapling the result. This Skill details the full workflow to distribute securely across macOS platforms.

How do I export compile_commands.json for IDE support in JUCE projects?

CMake projects can generate compile_commands.json as output to support IDE indexing and tooling integration. This Skill covers configuring CMake to export this file, enabling better editor support for JUCE plugin codebases.

Does AAX plugin building require special configuration or availability checks?

AAX availability and licensing requirements differ by platform and developer status. This Skill includes guidance on AAX availability checks, conditional compilation, and platform-specific build configurations to handle AAX format differences.

What are the differences between building VST3, AU, and AAX formats with CMake?

Each plugin format has distinct platform support, SDK requirements, and build flags. VST3 is cross-platform; AU is macOS-only; AAX requires licensing. This Skill explains format-specific CMake configurations and platform availability for each.