Pamplejuce Docs Getting Started How does this all work? Setting up your project Setting up Code Signing Customization File Management Including files outside of /source JUCE Adding JUCE Modules Private JUCE modules Dealing with Binary Data JuceHeader.h GitHub Actions 101 Tips and Gotchas How do GitHub variables work? Using self-hosted runners Using self-hosted runners as another user Life with Pamplejuce Adding Tests and Benchmarks Clang Format Managing Releases How to update your Project Other stuff The `SharedCode` interface target Example projects Original References & Insipration
Pamplejuce Docs > Getting Started > Setting up Code Signing
Table of Contents +

Setting up Code Signing

Code signing costs money. It’s around $100 year for each of the Apple and Microsoft platforms.

Set this up early. It will be an annoying as a TODO getting in the way of your launch! Plus, I’ve done all the hard work for you 🙂

Pamplejuce signs Windows via Azure Trusted Signing. Read more about how to set it up on my blog. I definitely recommend Azure, it’s less pain and instant reputation, compared with the “old school” EV signing.

It also code signs and notarizes on macOS. Again, you can read my article for details.

Removing code signing

IMO, code signing is a “must” in 2024 for anything you plan on selling to the general public. However, it’s trivial to remove if you want to “go green” (get your builds passing on GitHub Actions) for now or are just working on a personal project.

Simply remove the Codesign steps in .github/workflows/build_and_test.yml — on macOS, you’ll also have to look at the Create DMG, Notarize and Staple (macOS) step to remove Notarization.

< Previous
Setting up your projectNext >
File Management

Last Updated

Posted on 

 by sudara

Leave a Reply

Your email address will not be published. Required fields are marked *