From e71fd433f95f6a79db14c29fd470a95fc9f53d4b Mon Sep 17 00:00:00 2001 From: Robbert van der Helm Date: Wed, 6 May 2020 00:06:46 +0200 Subject: [PATCH] Clarify LoadLibrary() related startup error The old message sounds too much like something that would come from Linux's dynamic linker. --- CHANGELOG.md | 1 + src/wine-host/plugin-bridge.cpp | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 1ab87eab..e4bd76ef 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -14,6 +14,7 @@ Versioning](https://semver.org/spec/v2.0.0.html). symlinking plugins. Now you can use a symlink to a copy of `libyabridge.so` that's installed for a plugin in another directory. This is not recommended though. Fixes #3. +- Clarified the error that appears when we're unable to load the `.dll`. ### Fixed diff --git a/src/wine-host/plugin-bridge.cpp b/src/wine-host/plugin-bridge.cpp index 993ef007..052c0756 100644 --- a/src/wine-host/plugin-bridge.cpp +++ b/src/wine-host/plugin-bridge.cpp @@ -77,7 +77,7 @@ PluginBridge::PluginBridge(std::string plugin_dll_path, vst_host_aeffect(io_context) { // Got to love these C APIs if (plugin_handle == nullptr) { - throw std::runtime_error("Could not load a shared library at '" + + throw std::runtime_error("Could not load the Windows .DLL file at'" + plugin_dll_path + "'."); }