I’m trying to use the new moduleinfotool that came with 3.7.5 but unfortunately, it seems to be having issues loading the plugin to parse it. The LoadLibraryW call fails with an Access Denied error, I checked the code and the path to my vst seems fine. The permission on the file seems a bit odd but I changed to the windows equivalent of a 777 without any luck.
Am I missing something, does the tool need to be signed somehow? (I’m on Windows 11 using VS2022).
I realize that most hosts aren’t yet supporting this new json format, but I figured I might as well start using it.
the access denied error might be a red herring, after commenting out the moduleinfotool call, I noticed that the validator is also failing, but with a different error: failed: The specified module could not be found. I’ll dig more later to see if something my missing in my test plugin so it wouldn’t be valid. I kind of wish the validator was providing more useful information.
Well… turns out the issue was that my project was failing to link zlib which was the root cause of all my issues…
If anyone encounters a similar issue, the problem I run into was that I was linking against zlib on mac and coming to windows, I didn’t realize that the linkage will fail at runtime and not give me any feedback. I thought I was doing something wrong in my SDK implementation but it was good old Windows letting me know that I had a dependency that wasn’t available (I had to guess which one).