Skip to content

Commit 77252e2

Browse files
committed
Clarify JUCE 8 requirement when pluginval is a dependency [ci skip]
1 parent 061e056 commit 77252e2

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ cmake --build Builds/Debug --config Debug # build
3434

3535
### Including within an existing JUCE project
3636

37-
Instead of running as a separate app, you can add pluginval as a CMake target to your existing plugin project. This not only makes for a convenient debugging workflow, it gives you better stack traces.
37+
Instead of running as a separate app, you can add pluginval as a CMake target to your existing JUCE plugin project. This not only makes for a convenient debugging workflow, it gives you better stack traces.
3838

3939
For example, if you add pluginval as a git submodule like so:
4040
```
@@ -49,6 +49,7 @@ CPMAddPackage("gh:tracktion/pluginval#develop")
4949

5050
Then all you need to do is call `add_subdirectory ("modules/pluginval")` in your `CMakeLists.txt`. This should be done **after** your call to `juce_add_plugin`.
5151

52+
Note that only JUCE 8 is currently supported/tested for this method.
5253

5354
### Third-party Installation
5455
###### _Chocolatey (Windows):_

0 commit comments

Comments
 (0)