mirror/JUCE
1
0
Fork 0
mirror of https://github.com/juce-framework/JUCE.git synced 2026-01-09 23:34:20 +00:00
Code Activity

CMake: Allow VST3 manifest generation to run later in the build

Browse source
This commit is contained in:
reuk 2023-08-15 13:41:38 +01:00
parent a305646440
commit 308ae31810
No known key found for this signature in database
GPG key ID: FCB43929F012EE5C
2 changed files with 94 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

24
docs/CMake API.md
View file

@ -644,6 +644,17 @@ attributes directly to these creation functions, rather than adding them later.
`kARAPlaybackTransformationContentBasedFadeAtTail`,
`kARAPlaybackTransformationContentBasedFadeAtHead`
`VST3_AUTO_MANIFEST`
- May be either TRUE or FALSE (defaults to TRUE). When TRUE, a POST_BUILD step will be added to the
VST3 target which will generate a moduleinfo.json file into the Resources subdirectory of the
plugin bundle. This is normally desirable, but does require that the plugin can be successfully
loaded immediately after building the VST3 target. If the plugin needs further processing before
it can be loaded (e.g. custom signing), then set this option to FALSE to disable the automatic
manifest generation. To generate the manifest at a later point in the build, use the
`juce_enable_vst3_manifest_step` function. It is strongly recommended to generate a manifest for
your plugin, as this allows compatible hosts to scan the plugin much more quickly, leading to
an improved experience for users.
#### `juce_add_binary_data`
juce_add_binary_data(<name>
@ -704,6 +715,19 @@ If your custom build steps need to use the location of the plugin artefact, you
by querying the property `JUCE_PLUGIN_ARTEFACT_FILE` on a plugin target (*not* the shared code
target!).
#### `juce_enable_vst3_manifest_step`
juce_enable_vst3_manifest_step(<target>)
You may call this function to manually enable VST3 manifest generation on a plugin. The argument to
this function should be a target previously created with `juce_add_plugin`.
VST3_AUTO_MANIFEST TRUE will cause the VST3 manifest to be generated immediately after building.
This is not always appropriate, if extra build steps (such as signing or modifying the plugin
bundle) must be executed before the plugin can be loaded. In such cases, you should set
VST3_AUTO_MANIFEST FALSE, use `add_custom_command(TARGET POST_BUILD)` to add your own post-build
steps, and then finally call `juce_enable_vst3_manifest_step`.
#### `juce_set_<kind>_sdk_path`
juce_set_aax_sdk_path(<absolute path>)