On 04/04/2016 06:47 PM, Jonathan Wilkes via Pd-list wrote:
> However, when loading Gem I get errors like the following to stderr:
> dylib loading file 'gem_fileAVI.dll'!GemDylib failed: #126: The specified module could not be found.
>
> I also see this on the console:"please manually add 'blah/blah/blah/extra/gem' to your search path!
> gem_fileAVI.dll is in the same extra/Gem folder as Gem.dll.
> Shouldn't Windows search by default for library dependencies in the same
> directory as the library itself?
Gem is dlopen()ing (well LoadLibrary()ing) the plugins manually, so it
doesn't really matter where W32 is looking for them.
> Does "add manually" mean to add the search path
yes, this is what the message means.
afaict (googling for "LoadLibrary returns 126") the problem is that the
dependencies of gem_fileAVI.dll cannot be resolved.
use Dependency Walker or simile to find out what is missing.
also, i happily accept PRs for the Gem-wiki [1] detailing the process of
building Gem with msys2.
gfmstd
IOhannes
[1]
https://github.com/umlaeute/Gem/wiki clone as
https://github.com/umlaeute/Gem.wiki.git