feat(juce): let JUCE projects add the module through FetchContent

The top-level CMakeLists always looked up OpenSSL, and CURL unless
MOONBASE_USE_CURL was off, although the JUCE module needs neither. A JUCE
project therefore could not FetchContent_MakeAvailable() this repository
on a machine without them, and had to fetch the sources and call
juce_add_module() itself.

MOONBASE_JUCE_MODULE_ONLY (off by default) adds just the moonbase_licensing
module with JUCE's juce_add_module and leaves out the core SDK target and
everything built on it, so OpenSSL, CURL and nlohmann_json are never looked
up. JUCE has to be added first; the configure says so if it was not.

The JUCE workflow now configures with the option, and a new job builds
tests/juce_consumer_smoke, a JUCE project consuming the repository this
way, with the OpenSSL and CURL lookups disabled outright.

Author: TobbenTM

.github/workflows/juce.yml

@@ -7,7 +7,9 @@ name: JUCE module
 #
 # The suite signs tokens with OpenSSL then verifies them with the platform's
 # native backend, i.e. a real cross-backend RS256 round-trip on each OS. The
-# module needs no curl, so the build turns it off (-DMOONBASE_USE_CURL=OFF).
+# suite needs nothing from the core SDK target, so the build configures with
+# -DMOONBASE_JUCE_MODULE_ONLY=ON, which also skips its CURL lookup. OpenSSL is
+# still installed because the suite signs its test tokens with it.
 #
 # The module supports JUCE 6.1.3 and up, so the matrix also builds the two older
 # lines: 6.1.3 is what HISE pins, 7.0.12 is the last 7.x. They run on macOS only.
@@ -70,7 +72,7 @@ jobs:
         run: |
           cmake -S . -B build \
             -DCMAKE_BUILD_TYPE=Release \
-            -DMOONBASE_USE_CURL=OFF \
+            -DMOONBASE_JUCE_MODULE_ONLY=ON \
             -DMOONBASE_BUILD_JUCE_TESTS=ON \
             -DMOONBASE_JUCE_VERSION="${{ matrix.juce }}"
 
@@ -79,7 +81,7 @@ jobs:
         run: |
           cmake -S . -B build \
             -DCMAKE_BUILD_TYPE=Release \
-            -DMOONBASE_USE_CURL=OFF \
+            -DMOONBASE_JUCE_MODULE_ONLY=ON \
             -DMOONBASE_BUILD_JUCE_TESTS=ON \
             -DMOONBASE_JUCE_VERSION="${{ matrix.juce }}" \
             -DOPENSSL_ROOT_DIR="$(brew --prefix openssl@3)"
@@ -89,7 +91,7 @@ jobs:
         shell: bash
         run: |
           cmake -S . -B build \
-            -DMOONBASE_USE_CURL=OFF \
+            -DMOONBASE_JUCE_MODULE_ONLY=ON \
             -DMOONBASE_BUILD_JUCE_TESTS=ON \
             -DMOONBASE_JUCE_VERSION="${{ matrix.juce }}" \
             -DCMAKE_TOOLCHAIN_FILE="$VCPKG_INSTALLATION_ROOT/scripts/buildsystems/vcpkg.cmake" \
@@ -113,3 +115,26 @@ jobs:
       - name: Test
         if: runner.os != 'Linux'
         run: ctest --test-dir build -R "Juce\." -C Release --output-on-failure
+
+  # The route a JUCE project takes to consume this repository: JUCE first, then
+  # the repository as a subproject with MOONBASE_JUCE_MODULE_ONLY on. OpenSSL and
+  # CURL lookups are disabled outright, so a REQUIRED lookup creeping back onto
+  # that path fails the configure. One OS is enough: the regression is a CMake
+  # one, and the module's compile is covered on every OS above.
+  module-only-consumer:
+    name: module-only consumer (macos-14)
+    runs-on: macos-14
+    timeout-minutes: 30
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Configure
+        run: |
+          cmake -S tests/juce_consumer_smoke -B build-juce-consumer \
+            -DCMAKE_BUILD_TYPE=Release \
+            -DCMAKE_DISABLE_FIND_PACKAGE_OpenSSL=ON \
+            -DCMAKE_DISABLE_FIND_PACKAGE_CURL=ON
+
+      - name: Build
+        run: cmake --build build-juce-consumer --target MoonbaseJuceConsumerSmoke --config Release -j

.releaserc.json

@@ -23,6 +23,7 @@
           "CMakeLists.txt",
           "README.md",
           "docs/core-sdk.md",
+          "docs/juce-module.md",
           "modules/moonbase_licensing/moonbase_licensing.h"
         ],
         "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"