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 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 > Life with Pamplejuce > How to update your Project
Table of Contents +

How to update your Project

Because Pamplejuce is a template and not a framework, you’ll have to this somewhat manually. Sorry!

Here are the steps I do:

  1. Update with the latest CMake version listed here. If you are on VS or CLion, this is all managed for you as you upgrade, so you can skip this.
  2. Update JUCE with git submodule update --remote --merge JUCE
  3. Update the inspector with git submodule update --remote --merge modules/melatonin_inspector
  4. If you use IPP, check for an IPP update from Intel.
  5. If you want to update to the latest CMake config Pamplejuce uses, first check the repository’s CHANGELOG to make sure you are informed of any breaking changes. Then git submodule update --remote --merge cmake.
  6. Unfortunately, you’ll have to manually compare CMakeLists.txt, but most of the time it should be pretty easy to see what changed.

< Previous
Managing ReleasesNext >
The `SharedCode` interface target

Last Updated

Posted on 

 by sudara

Leave a Reply

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