MOSAC: A Local Multi-Platform Build & Cross-Compilation CLI Tool for JUCE C++ Projects

Hi everyone, I would like to introduce MOSAC, a CLI tool written in Golang designed to automate and streamline local build pipelines for Plugin Audio Basic projects built on the JUCE Framework (C++).

Target Audience & Primary Use Case

MOSAC is geared towards indie developers, small teams, and academic research labs operating with limited budgets. Its main goal is to provide a fully local alternative to cloud-based CI/CD infrastructure, delivering end-to-end multi-platform deployment for MacOS, Windows, and Linux directly on your local setup.

Pipeline Architecture & Cross-Compilation

  • macOS: Native compilation executed via the xcodebuild toolchain.

  • Linux & Windows: Virtualized execution using two dedicated Linux-based Docker containers. The Linux binary is compiled natively inside its container, whereas the Windows target is cross-compiled using the LLVM toolchain paired with Windows SDKs extracted via xwin.

Operational Features & Supported Formats

The build process runs sequentially to ensure deterministic artifact generation and precise system resource allocation. It supports both Debug and Release target configurations, covering standard JUCE output formats: Standalone, VST3, LV2, AU, AAX, and Unity.

Real-World Application & Validation

MOSAC is already deployed in production and actively used in close synergy with the LIM Plugin Collection (https://audioplugins.lim.di.unimi.it/), at the University of Milan.

Any technical feedback, questions, or suggestions from the developer and DSP community are welcome!
Carlo A.

[ Link to the GitHub repo: GitHub - LIMUNIMI/mosac: An automatic cross-compiling system for C/C++ JUCE audio plugins. · GitHub ]

2 Likes

Altough I’m very happy with CMake-based cross platform build setups, you got my attention when reading that it does cross-compiling to Windows on a Linux host. As far as I can see from quickly scanning over the docs, this consumes Projucer based projects configured with the .jucer file format and does not make that possible for modern CMake-based JUCE projects, so you don’t have to deal with building the juceaide helper executable for any of this, right?

Sorry for the delay! :slight_smile:

mosac currently only supports projects that include a .jucer file. Under the hood, a CMakeLists.txt file is generated with ad-hoc configurations tailored specifically for Linux-to-Windows cross-compilation (I might decouple the JUCE API setup from the rest of the CMake configuration in a future update).

The juceaide helper tool is compiled natively for Linux inside the Docker image used for the Windows cross-compilation (there are no emulators or Wine involved). I haven’t touched any internal build logic of the standard JUCE compilation pipeline.

Here is an output snippet from MOSAC during a plugin build:

[DockerManager] Docker already running.
[WindowsBuilder] Preparing environment...
[DockerManager] Image already built.
[DockerManager] Creating container from juce-builder:windows...
[DockerManager] Container started. Execution of command in progress...

-- The C compiler identification is Clang 19.1.0 with MSVC-like command-line
-- The CXX compiler identification is Clang 19.1.0 with MSVC-like command-line
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/local/bin/clang-cl - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/local/bin/clang-cl - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring juceaide
-- Building juceaide
-- Exporting juceaide
-- Testing juceaide
-- Finished setting up juceaide
-- Looking for pthread.h
-- Looking for pthread.h - not found
-- Found Threads: TRUE
-- Configuring done
-- Generating done
-- Build files have been written to: /workspace/build/Windows/Release
[0/2] Re-checking globbed directories...

As you can see, juceaide is compiled successfully for Linux, and the build proceeds without any issues from that point on. To be honest, I didn’t even have to think about it lol :sweat_smile: