Instead of just detaching the threads, it's much better to terminate the
Wine process and let the threads terminate themselves.
This fixes#11 on my machine.
Now that I think about it it's pretty obvious why symlinks only work
with hosts that support plugin sandboxing (since your OS will never load
two instaces of an identical .so file into the same process). Still, I
find using symlinks in hosts that do sandbox their plugins to be very
user friendly, especially while developing.
This is for data passed through the `value` `intptr_t` parameter. The
only two events that use this are `effSetSpeakerArrangement` and
`effGetSpeakerArrangement`. Since this is such a rare occurrence we'll
leave the regular `value` field as it is.
As mentioned in the last commit. The original reasoning behind these
names was that the HostBridge talks to the host, and the PluginBridge
talks to the plugin, but you could also argue that the HostBridge should
be part of the Wine VST host and the PluginBridge should be part of the
VST plugin. This removes that ambiguity.
I had swapped these names around once before but I think going with
PluginBridge for the plugin and WineBridge for the Wine VST host is the
least ambiguous it can get.
These are now built into the image since building the minimal version of
Boost we need took minutes on the CI machines even though it should only
a few seconds.
Squash of the following commits:
WIP: Build workflow on all branches
WIP: Reduce noise from wget
WIP: Don't use bash-style redirects
WIP: Use variables for Boost url and checksum
WIP: Manually set a Wine prefix
The user that's executing the job does not own the home directory for
some reason.
WIP: Fix typos in workflow
WIP: Don't use bash-style brace expansion
This is run under dash.
WIP: Fix archive name for Ubuntu 20.04 build
WIP: Fetch tags for git-describe
WIP: Fetch all git history for git-describe
WIP :Rename the workflow
Since this is what will appear on the status badge.
Robbert van der Helm