VCV Rack Plugin Toolchain - Updates

CircadianSound · March 31, 2025, 12:20am

So will passing the number of cores using JOBS=4 and then using -j4 still work? Or should we be using nproc instead? Or are you saying that the important part is to define JOBS using JOBS=$(nproc) , as skipping this step will result in the build not working?

Bloodbat · March 31, 2025, 6:15am

Thanks

Chinenual · March 31, 2025, 11:54pm

My plugin github workflow is based on GitHub - qno/vcv-plugin-github-actions-example: Example repository for building and publishing a VCV Rack plugin with GitHub Actions., but fails with the latest release.

The first problem I’m encountering is that the qno code attempts to wget the mac VCV SDK as a .zip file, but it seems that since 2.6.0, it’s being published as a .pkg file.

Before I spend too much time trying to figure out how to fix, has anyone already solved this problem?

--2025-03-31 23:42:12--  https://vcvrack.com/downloads/Rack-SDK-latest-mac-x64+arm64.zip
Resolving vcvrack.com (vcvrack.com)... 107.191.126.116
Connecting to vcvrack.com (vcvrack.com)|107.191.126.116|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: Rack-SDK-2.6.3-mac-x64+arm64.zip [following]
--2025-03-31 23:42:12--  https://vcvrack.com/downloads/Rack-SDK-2.6.3-mac-x64+arm64.zip
HTTP request sent, awaiting response... 404 Not Found
2025-03-31 23:42:12 ERROR 404: Not Found.

Error: Process completed with exit code 8.

Thanks! Steve

Bloodbat · April 1, 2025, 12:08am

The problem is that the SDK has been split. That problem has been solved:

github.com/Bloodbat/SanguineMutants

.github/workflows/nightly_builds.yml

02a801db2


      
                run: |
                  export PLUGIN_DIR=$GITHUB_WORKSPACE
                  pushd ${{ env.rack-plugin-toolchain-dir }}
                  make plugin-build-${{ matrix.platform }}
              - name: Upload artifact
                uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02
                with:
                  path: ${{ env.rack-plugin-toolchain-dir }}/plugin-build
                  name: ${{ matrix.platform }}
          
          build-mac:
            name: mac
            needs: modify-plugin-version
            runs-on: macos-latest
            strategy:
              fail-fast: false
              matrix:
                platform: [x64, arm64]
            steps:
              - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
                with:

The problem with the current SDK are Windows builds, as discussed above, though it shouldn’t affect your builds if you are using Qno’s image.

Chinenual · April 1, 2025, 12:35pm

Thanks @Bloodbat -

For others, it’s just a one-line fix to make the qno example work with the current SDK:

~/src/vcv-plugin-github-actions-example> git diff
diff --git a/.github/workflows/build-plugin.yml b/.github/workflows/build-plugin.yml
index 6e29e0d..95112d1 100644
--- a/.github/workflows/build-plugin.yml
+++ b/.github/workflows/build-plugin.yml
@@ -79,7 +79,7 @@ jobs:
       - name: Get Rack-SDK
         run: |
           pushd $HOME
-          wget -O Rack-SDK.zip https://vcvrack.com/downloads/Rack-SDK-${{ env.rack-sdk-version }}-mac-x64+arm64.zip
+          wget -O Rack-SDK.zip https://vcvrack.com/downloads/Rack-SDK-${{ env.rack-sdk-version }}-mac-${{ matrix.platform }}.zip
           unzip Rack-SDK.zip
       - name: Build plugin
         run: |

I’ve submitted a PR to the qno project;

phantombeta · April 1, 2025, 1:31pm

I think it’s worth noting that qno’s Actions workflow uses a forked version of VCV’s toolchain image for the Windows and Linux builds. Changing that line will make the Mac OS builds use the 2.6.3 SDK, while the other builds will still be building against the 2.5.2 toolchain