Pamplejuce is a template lifestyle for creating and building JUCE plugins in 2021.

Out of the box, it supports:

1. C++20
2. JUCE 6.x as a submodule, tracking develop
3. CMake 3.18 (Latest bundled version in VS 2019 as of Jan 2021)
4. Catch2 2.13.3
5. Github Actions for both CI and artifact building
6. Proper .gitignore given the above
7. Building on Windows, Linux and Mac (including arm64 built with Xcode 12.2)

What it doesn't handle (yet)

1. MacOS code signing, packaging, notarization.

How to setup the repo for YOUR project

This is a template repo!

Yeah, I didn't know GitHub had these either. You can kickstart your new repo using this one as the base by clicking "Use this template" at the top of the page.

After you have your own repo:

1. Download CMAKE if you are on MacOs or Linux. VS 2019 has it bundled.

2. Get the latest JUCE by running git submodule update --init in your repository directory. By default this will track JUCE's develop branch.

3. Replace Pamplejuce with the name of your project in CMakeLists.txt line 5, where the PROJECT_NAME variable is set.

4. Pick which formats you want built on line 8.

5. Set the correct flags for your plugin under juce_add_plugin. Check out the API https://github.com/juce-framework/JUCE/blob/master/docs/CMake%20API.md and be sure to change things like PLUGIN_CODE and PLUGIN_MANUFACTURER_CODE

Conventions

1. Your tests will be in "Tests"
2. Your binary data target is called "Assets"

Tips n' Tricks

⚠️ GitHub might give you 2000 or 3000 free GitHub Actions "minutes" for private projects, but they bill 2x the number of minutes you use on Windows and 10x on MacOS!

Always manually add new Source/Test files to CMakeLists.txt

One might think that in 2021, files added to your Sources directory would automatically added to a target.

It's true, you could use globbing. But "Modern CMake" distinctly prohibits this — why? Because CMake has no way of reliabily knowing you've added a new file, so it won't be picked up.

How does this all work at a high level?

The CMakeLists.txt file describes how to configure and build the plugins as well as setup the IDE project.

Unfortunately, these different jobs are not clearly separated or delineated by CMake's config, CLI or options. In my opinion, this is why CMake has the reputation it has: there's a lot of complexity resulting from implicit coupling between these concerns.

JUCE provides cmake helpers, allowing plugin devs to call a small number of functions like juce_add_plugin. It sets up our project much like JUCE's Projucer did in the past, generating the IDE project and setting up all the build config files.

GitHub Actions is running CMake on MacOS, Windows and Linux, therefore configuring, building and testing for each environment.

CMak does its jobs for us in multiple incantations:

1. Configure

The CMakeLists.txt is parsed, processed and the project is configued.

This might look something like cmake -B Builds

The -B option tells CMake what folder to perform the build in, where to stick all the resultant files, etc.

2. Generate

This outputs files for system specific build tooling and IDEs to read.

Generate a VS 2019 Project file:

cmake -B Builds -G "Visual Studio 16 2019"

Or an Xcode project:

cmake -B Builds -G Xcode

During local JUCE development, we'd run one of the above and then trigger actual builds from our IDE rather than CMake.

3. Build

You can skip the IDE project generation but still build using the system specific build tools (such as Xcode) on the command line with:

cmake --build Builds --config Release

This is how GitHub Actions builds.

4. Test

Again, things are messy and lines are blurred.

CTest is just a unit test runner. It doesn't know anything about unit test implementation or know anything about the executable that it will run.

So a test executable has to be created by CMake first, which we are doing with the help of the Catch2 CMake integration.

Testing is enabled with enable_testing() in a CMakeLists.txt file and then the ctest command can be run in the Builds directory

When run, ctest will barfs up logs in Testing/Temporary. Thanks, ctest.

Since tests are an executable target, they are built and run via Xcode schemes, with results showing up in the console:

5. Package

TBD.

How do variables work in GitHub Actions?

It's very confusing, as the documentation is a big framented.

1. Things in double curly braces like ${{ matrix.artifact }} are called "contexts or expressions" and can be used to get, set, or perform simple operations.
2. In "if" conditions you can omit the double curly braces, as the whole condition is evaluated as an expression: if: contains(github.ref, 'tags/v')
3. You can set variables for the whole workflow to use in "env"
4. Reading those variables is done with the env context when you are inside a with, name, or if: ${{ env.SOME_VARIABLE }}
5. Inside of run, you have access to bash ENV variables in addition to contexts/expressions. That means $SOME_VARIABLE or ${SOME_VARIABLE} will work but only when using bash and not while using powershell on windows. The version with curly braces (variable expansion) is often used when the variable is forming part of a larger string to avoid ambiguity. Be sure that the ENV variable was set properly in the workflow/job/step before you use it. And if you need the variable to be os-agnostic, use the env context.

References & Inspiration

CMake

• The "Modern CMake" gitbook which also has a section on https://cliutils.gitlab.io/modern-cmake/chapters/testing/catch.html.
• Effective Modern CMake
• JUCE's announcment of native CMake support
• Eyalamir Music's JUCE / CMake prototype repository

GitHub Actions

• Christian Adam's HelloWorld CMake and ccache repo
• Maxwell Pollack's JUCE CMake + GitHub Actions repo
• Oli Larkin's PDSynth iPlug2 template

Catch2 & CTest

• Catch2's docs on CMake integration
• Roman Golyshev's Github Actions & Catch2 repo
• Matt Clarkson's CMakeCatch2 repo
• CMake Cookbook example
• Unit Testing With CTest
• Mark's Catch2 examples from his 2020 ADC talk

Packaging & Notorization (tbd)

• iPlug Packages and Inno Setup scripts
• Surge's pkgbuild installer script
• Chris Randall's PackageBuilder script
• David Cramer's GA Workflow for signing and notarizing and his notarize-cli tool

Pamplejuce dev

I've been blowing away the Builds directory when altering the CMake.

rm -rf Builds && cmake -B Builds -G Xcode
rm -rf Builds && cmake -B Builds && cmake --build Builds --config Release 

Updating

1. Update with latest CMake version listed here. Note that VS 2019 has a bundled CMake and tends to run behind, so this might be the limiting factor for CMake versions.
2. Update JUCE with git submodule update --remote --merge
3. Update Xcode to latest available version and change DEVELOPER_DIR env var in the GitHub action.
4. Change Catch2 version in CMakeLists.txt to latest tag