📈
juce-cookbook
  • Introduction
  • Getting Started
    • Why JUCE?
    • Other Libraries
    • Resources
  • C++
    • IDE
    • Tools
    • Resources
  • Setup
    • macOS
    • Windows
    • Linux
    • Projucer vs. CMake
    • Create Project
    • Debugging
    • Documentation
  • Coding
    • User Interface
      • Component
      • Button
      • Look&Feel
    • Plug-in
      • Basics
      • Parameter
    • DSP
      • Basics
      • Create your own
    • Modules
    • Misc
    • Examples
    • Snippets
  • Testing
    • Unit tests
    • pluginval
    • Sanitizers
    • Profile
    • Benchmark
  • Continuous Integration
    • Travis CI
    • AppVeyor
    • Publish
  • Wish List
  • What's next
  • License
Powered by GitBook
On this page
  • Project Types
  • Project Management
  • Projucer
  • CMake

Was this helpful?

Setup

PreviousResourcesNextmacOS

Last updated 4 years ago

Was this helpful?

Project Types

Project Management

If you have multiple projects on your machine that use JUCE, you get to a problem where you update to a new release and now you have to check all of your projects if they still compile & work. Using git submodules solves this problem. You essentially have a copy of JUCE for each of your projects and the exact version is saved in your git history. Know updating to new JUCE version can be done on a per project basis.

cd $PROJECT_ROOT
mkdir 3rd_party
git submodule add https://github.com/juce-framework/JUCE 3rd_party/JUCE

# optional
cd 3rd_party/JUCE
git checkout juce6

Projucer

  • Update module paths to new location

  • Make sure it's done for each exporter

CMake

  • Update path in add_subdirectory

Official JUCE: Choosing the right Projucer template for your application