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 > 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. If you want to update JUCE: git submodule update --remote --merge JUCE
  2. Update the melatonin inspector with git submodule update --remote --merge modules/melatonin_inspector
  3. If you use IPP, you can check for an IPP update from Intel.
  4. If you want to update to the latest CMake config, first check the repository’s CHANGELOG to make sure you are informed of any breaking changes. Then git submodule update --remote --merge cmake.
  5. You’ll have to manually compare your CMakeLists.txt against the latest Pamplejuce for changes, but 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 *