Kim T

Another workaround solution using github-script: ```yaml - name: Create Release uses: actions/github-script@v2 with: github-token: ${{secrets.GITHUB_TOKEN}} script: | console.log('environment', process.versions); const fs = require('fs').promises; const { repo: { owner, repo },...

> ```yaml > - name: Create Release > uses: actions/github-script@v2 > with: > github-token: ${{secrets.GITHUB_TOKEN}} > script: | > console.log('environment', process.versions); > > const fs = require('fs').promises; > > const...

I have a workaround for this which creates the release first, before going into matrix mode: ``` jobs: create_release: name: Create release runs-on: ubuntu-latest outputs: upload_url: ${{ steps.create_release.outputs.upload_url }} steps:...

Looks like someone started a PR here: https://github.com/iPlug2/iPlug2/pull/579 To me it would make more sense to add CMake support rather than adding lots of custom CI scripts: https://github.com/iPlug2/iPlug2OOS/tree/master/TemplateProject/scripts **For comparison**...

Thanks for the quick response. I'm not an expert on cmake, but can help test on a mac if that helps! I'm working on an open-source audio plugin templates/registry/manager/app: https://github.com/studiorack...

Thanks will take a look at the issue you created. I found another build error with Linux: ``` cmake \ -G "Unix Makefiles" \ -DCMAKE_BUILD_TYPE=Release \ -S ./iplugsdk/Examples/IPlugInstrument \ -B...

Been working on the GitHub Actions to automatically build iPlug plugins using cmake. It's working and publishing Linux and Mac plugins as GitHub releases here: https://github.com/studiorack/studiorack-plugin-iplug Some changes I had...

winexport.def fix didn't seem to work for me. So i'm still reverting VST3_SDK to a previous commit. Managed to get IPlugInstrument to build using cmake for Linux, MacOS and Windows...

I have the one example building nicely with my overwrites: https://github.com/studiorack/studiorack-plugin-iplug I want to build multiple iPlug examples using cmake, for that I need to have a parent CMakeLists.txt file...

It might be worth also checking the Steinberg VST3 nested cmake setup, which allows you to build all examples in one go: https://github.com/steinbergmedia/vst3_public_sdk https://github.com/steinbergmedia/vst3_public_sdk/tree/master/samples/vst Not sure if that is an...