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 > JUCE > JuceHeader.h
Table of Contents +

JuceHeader.h

Using JuceHeader.h has been deprecated for some time — if this is a new project, definitely avoid it!

Instead, directly include the .h files you need from the juce modules you are using, like so: #include "juce_gui_basics/juce_gui_basics.h"

If you are converting an older project, it’s still worth the conversion away from JuceHeader.h to using the actual juce modules you need. You’ll get faster compilation, autocomplete, etc.

You can see an example of the conversion I did for pluginval. It’s less scary than you think. Just make sure the juce:: prefix is added everywhere, try to compile and your IDE will yell at you to clean everything else up 🙂

< Previous
Dealing with Binary DataNext >
Tips and Gotchas

Last Updated

Posted on 

 by sudara

Leave a Reply

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