Clarify LoadLibrary() related startup error

The old message sounds too much like something that would come from
Linux's dynamic linker.
This commit is contained in:
Robbert van der Helm
2020-05-06 00:06:46 +02:00
parent 750130e4a5
commit e71fd433f9
2 changed files with 2 additions and 1 deletions
+1
View File
@@ -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
+1 -1
View File
@@ -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 + "'.");
}