JUCE TUTORIALS. INTRO methodology how to create a GUI APP and how to create a Plugin.

Transcription

1 JUCE TUTORIALS INTRO methodology how to create a GUI APP and how to create a Plugin. Install Juice and Xcode (or other IDE) Create a project: GUI Application Select platform Choose Path, Name, Folder Name Save Project and Open in IDE Check Files Build Main.cpp Check Build and Run ATTENTION 1) sometimes the location of Juce modules is underlying ~/modules or ~/juce/module create both. 2) To load a project always use: Save Project and Open in IDE So that the paths are saved. Otherwise might not work.

2 Structure of Projucer projects Below is the folder structure of a JUCE project that the Projucer generates for you: At the top level is the.jucer file (highlighted above), which contains all project settings. In addition to the.jucer file, three subfolders are generated: Folder Content Source The C++ source code of your JUCE app. The export targets generated by the Projucer. The Xcode project file and Visual Studio solution are highlighted as an example in the screenshot Builds above. Open these files to start coding, debugging, and running your JUCE app. Here are some auto-generated header files that include the JUCE library JuceLibraryCode code via the JUCE modules. Note that the actual JUCE library code is not located here, but inside your global JUCE folder that you installed earlier. Managing your project Now we will have a look at the most essential features of the Projucer that you will frequently use as you develop your JUCE app.

3 Adding and editing source files The projucer offers a file browser and a basic code editor for C++ source files. It is located under the Files tab. This is what it looks like: The Projucer file navigator (left) and source file editor (right). With the Projucer, you can add new source files to your project and delete or rename existing ones, as well as organise files into groups with right click. Note Groups are not the same as folders. If you create a file in a group in Projucer, you will also be asked in which folder to save the file. With this, it is possible to have a folder structure that is different from the group structure. However, it is highly recommended and good practice to have your groups follow the structure and names of the folders. If you make changes to the file structure and then save the project afterwards, your changes will be reflected in all native IDE projects that are exported. In this way, you can easily keep the file structure of the project consistent across all platforms you are developing on. Warning You should never add, rename, and/or remove source files from JUCE projects inside your native IDE (such as Xcode, Visual Studio). These changes would be overwritten the next time you save the project in Projucer (which re-generates the native IDE projects every time). Instead, always use the Projucer itself to make such changes. The Projucer's code editor appears when you select a file in the file browser. To do some quick changes to your code, you don't need to fire up a native IDE, instead just make the changes in the Projucer and save your changes.

4 Managing JUCE modules The JUCE library code is organised into different modules. By default, all modules that are needed for the type of your project are added. You can also manually add or remove modules in the Config tab by right-clicking on the red module icons in the configuration browser: The JUCE modules used by this project (left, highlighted) and module settings page (right). Most JUCE modules require other JUCE modules to properly compile. If you ever remove a module on which other modules of your project depend on, then the Projucer will highlight the now "broken" modules in red. You must then either remove the "broken" modules or add the missing modules. PATHS If you click on Modules in the browser (the first item under the project name), the module settings page opens. It provides an overview over all currently used modules and allows you to set the paths to them. To change the paths of all modules at once, enter the correct path into one of the modules, select it, and click on Set paths for all modules... The Download and add a module... button gives you access to additional JUCE modules that are not pre-installed by default. If you click on an individual module in the browser, you get access to module-specific settings and properties. There, you can check the version and licence of a particular module, and set the paths to additional dependencies such as SDKs and external libraries that a particular module is using. Usually, the default settings work just fine and you should rarely need to go into this page. Export targets, configurations, and build settings In the Config browser under the modules you can find the different export target that you created earlier (Xcode, Visual Studio, and so on). If you click on these in the browser, you get access to the build settings for this export target. This is the place to specify additional compiler and linker flags and other platform-specific build settings. To create a new export target for an additional IDE and platform, right-click on the project name at the top (with the JUCE icon) and select Create a new... target. You can do this at any time. For example, if you originally created a JUCE application for Windows and OSX, but then later you decided to also add support for Linux, you can do it with ease.

5 You can also delete export targets by right-clicking on them and selecting Delete this exporter. The Projucer creates build configurations to each export target which your native IDE will use to actually compile and run your app. By default, the two configurations Debug and Release are added to every export target. By clicking on these configurations, you can access the platformspecific build settings for this particular configuration: The different IDE configurations (left, highlighted) and configuration-specific build settings (right). You can add additional configurations as well. For example, for Visual Studio export targets the Projucer adds Debug and Release configurations using 32-bit. However, you may also want to add 64-bit support to your Windows app. For this, you can copy the two existing configurations (rightclick on the configuration and select Create a copy of this configuration), rename the copies to Debug64 and Release64, respectively, and then change the configuration build setting Architecture from 32-bit to 64-bit for both configurations.