mirror of
https://github.com/juce-framework/JUCE.git
synced 2026-01-10 23:44:24 +00:00
CMake: Add juce_enable_copy_plugin_step function
This commit is contained in:
parent
65bdf50d93
commit
3f17cc7b2e
2 changed files with 57 additions and 17 deletions
|
|
@ -589,6 +589,24 @@ disabled by setting the compile definitions `DONT_SET_USING_JUCE_NAMESPACE` and
|
|||
JuceHeader.h is optional. Instead, module headers can be included directly in source files that
|
||||
require them.
|
||||
|
||||
#### `juce_enable_copy_plugin_step`
|
||||
|
||||
juce_enable_copy_plugin_step(<target>)
|
||||
|
||||
As an alternative to the JUCE_COPY_PLUGIN_AFTER_BUILD property, you may call this function to
|
||||
manually enable post-build copy on a plugin. The argument to this function should be a target
|
||||
previously created with `juce_add_plugin`.
|
||||
|
||||
JUCE_COPY_PLUGIN_AFTER_BUILD will cause plugins to be installed 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 install. In such cases, you should leave JUCE_COPY_PLUGIN_AFTER_BUILD
|
||||
disabled, use `add_custom_command(TARGET POST_BUILD)` to add your own post-build steps, and then
|
||||
finally call `juce_enable_copy_plugin_step`.
|
||||
|
||||
If your custom build steps need to use the location of the plugin artefact, you can extract this
|
||||
by querying the property `JUCE_PLUGIN_ARTEFACT_FILE` on a plugin target (*not* the shared code
|
||||
target!).
|
||||
|
||||
#### `juce_set_<kind>_sdk_path`
|
||||
|
||||
juce_set_aax_sdk_path(<absolute path>)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue