I’m trying to build using MSYS2 on Windows 10; but I ran into this problem during the “make dep” stage. I understand the issue and even what the fix should be; since it amounts to applying this patch
What I don’t understand is how to make the solution work in the workflow of the build system. It seems that if I apply the patch and restart “make dep”, the build system overwrites the patched file with the original.
Can someone point me at a resource for how to make something like this work in the MSYS2 build workflow?
VCV used to use github issues for bug reporting, so you could watch this stuff. I guess now you use this stuff people used to call “e mail” to report bugs. But I have seen on discord that they are at least aware that one can’t build VCV by following the instructions on Windows.
I just reverted my gcc to get around this. Now I just never update anything and I’m good.
Thanks. I missed that in my quick search. However, the upshot is that VCV needs to upgrade their version of curl because the one they are using has security problems. I think I’ll contact support and wait until they do.
The only thing the ssl/curl impact is Rack accessing its own servers for updates/checking the plugin DB, so I’m a little less concerned than if it was a service to plugins that would access a wider web.
For my own use, I apply a patch to rtmidi for a bug in it, and also patch Rack’s own rtmidi wrapper to fix a Rack bug (reported a while back, but never fixed).