@@ -8,18 +8,19 @@ include (PamplejuceVersion)
8
8
9
9
# Change me!
10
10
# This is the internal name of the project and the name of JUCE's shared code "target"
11
- # Note: This cannot have spaces. It may be 2023, but you can't have it all.
12
- # Worry not, JUCE's PRODUCT_NAME can have spaces (and is external facing).
11
+ # Note: This cannot have spaces (it may be 2023, but you can't have it all!)
12
+ # Worry not, JUCE's PRODUCT_NAME can have spaces (and is DAWs display)
13
13
# You may want to append the major version on the end of this (and PRODUCT_NAME)
14
14
# set(PROJECT_NAME "MyPlugin_v${MAJOR_VERSION}")
15
15
# Doing so enables major versions to show up in IDEs and DAWs as separate plugins
16
- # allowing you to change parameters and behavior without breaking user projects
16
+ # allowing you to change parameters and behavior without breaking existing user projects
17
17
set (PROJECT_NAME "Pamplejuce" )
18
18
19
+ # Change me! Used for the MacOS bundle identifier
19
20
set (BUNDLE_ID "com.pamplejuce.pamplejuce" )
20
21
21
- # Set the plugin formats you'll be building here.
22
- # Valid choices here : AAX Unity VST VST3 AU AUv3 Standalone
22
+ # Change me! Set the plugin formats you want built
23
+ # Valid choices: AAX Unity VST VST3 AU AUv3 Standalone
23
24
set (FORMATS Standalone AU VST3 AUv3)
24
25
25
26
# For simplicity, the name of the CMake project is also the name of the target
@@ -37,7 +38,7 @@ include(JUCEDefaults)
37
38
# On Github Actions, this is done as a part of actions/checkout
38
39
add_subdirectory (JUCE)
39
40
40
- # Add your modules here
41
+ # Add any other modules you want modules here, before the juce_add_plugin call
41
42
# juce_add_module(modules/my_module)
42
43
43
44
# This adds the melatonin inspector module
@@ -52,7 +53,7 @@ juce_add_plugin("${PROJECT_NAME}"
52
53
COMPANY_NAME Pamplejuce
53
54
BUNDLE_ID "${BUNDLE_ID} "
54
55
55
- # On MacOS, plugin is copied to ~/Users/you /Library/Audio/Plug-Ins/
56
+ # On MacOS, plugin is copied to ~/Users/yourname /Library/Audio/Plug-Ins/
56
57
COPY_PLUGIN_AFTER_BUILD TRUE
57
58
58
59
# Change me!
@@ -91,9 +92,10 @@ target_sources(SharedCode INTERFACE ${SourceFiles})
91
92
# Adds a BinaryData target for embedding assets into the binary
92
93
include (Assets)
93
94
94
- # MacOS only: Clean up folder organization on Xcode.
95
- include (Xcode )
95
+ # MacOS only: Cleans up folder and target organization on Xcode.
96
+ include (XcodePrettify )
96
97
98
+ # This is where you can set preprocessor definitions for JUCE and your plugin
97
99
target_compile_definitions (SharedCode
98
100
INTERFACE
99
101
@@ -113,10 +115,11 @@ target_compile_definitions(SharedCode
113
115
PRODUCT_NAME_WITHOUT_VERSION="Pamplejuce"
114
116
)
115
117
116
- # Usually JUCE modules should have PRIVATE visibility
118
+ # Link to any other modules you added (with juce_add_module) here!
119
+ # Usually JUCE modules must have PRIVATE visibility
117
120
# See https://github.com/juce-framework/JUCE/blob/master/docs/CMake%20API.md#juce_add_module
118
- # However, with Pamplejuce, you will link your modules to SharedCode with INTERFACE visibility
119
- # This allows JUCE targets and the Tests target to link against it
121
+ # However, with Pamplejuce, you'll link modules to SharedCode with INTERFACE visibility
122
+ # This allows the JUCE plugin targets and the Tests target to link against it
120
123
target_link_libraries (SharedCode
121
124
INTERFACE
122
125
Assets
0 commit comments