hi, dear list !
i recently did a successful self-compiling of the latest PD sources with Msys2 on my Windows 7 system, following lucardas instructions (which is basically a shorthand of the INSTALL.txt file that comes along with the latest PD sources).
everything went well - i had no errors in the compilation process and received a working pd-0.49.0
i also tried external libraries, all of them were perfectly loading and working, save for (you guessed it by the subject): Gem
==================================================== C:\pd-0.49.0\extra\Gem\Gem.dll: couldn't load Gem: can't load library ====================================================
(unfortunately also error-level 4 did not print anything more)
I had no trouble loading Gem.dll with the precompiled pd-0.49.0 from miller's site, so i'm wondering what went wrong on my compiled version.
would i need some special configure options for Gem to work ?
thanks for any helps and hints !
best
oliver
On 03.12.18 02:31, oliver wrote:
hi, dear list !
i recently did a successful self-compiling of the latest PD sources with Msys2 on my Windows 7 system, following lucardas instructions (which is basically a shorthand of the INSTALL.txt file that comes along with the latest PD sources).
everything went well - i had no errors in the compilation process and received a working pd-0.49.0
i also tried external libraries, all of them were perfectly loading and working, save for (you guessed it by the subject): Gem
==================================================== C:\pd-0.49.0\extra\Gem\Gem.dll: couldn't load Gem: can't load library ====================================================
suspect #1: are you by-chance trying to load a 32bit version of Gem into a 64bit version of Pd? that won't work. both the host (Pd) and the external (Gem) must have the same "architecture".
suspect #2: the usual mismatch between msvcr90.dll (missing from the Gem distribution) and the likes. the mailinglist archives should cover this.
just for the record: i can load Gem-0.93.3 ("Windows Archive (binaries + documentation)", so that's the ZIP version), just fine with Pd-0.49-0-i386 (ZIP version as well), using "wine" (not having tried it on a native windows machine)
fgmasdr IOhannes
IOhannes m zmoelnig wrote:
On 03.12.18 02:31, oliver wrote:
hi, dear list !
i recently did a successful self-compiling of the latest PD sources with Msys2 on my Windows 7 system, following lucardas instructions (which is basically a shorthand of the INSTALL.txt file that comes along with the latest PD sources).
everything went well - i had no errors in the compilation process and received a working pd-0.49.0
i also tried external libraries, all of them were perfectly loading and working, save for (you guessed it by the subject): Gem
==================================================== C:\pd-0.49.0\extra\Gem\Gem.dll: couldn't load Gem: can't load library ====================================================
suspect #1: are you by-chance trying to load a 32bit version of Gem into a 64bit version of Pd? that won't work. both the host (Pd) and the external (Gem) must have the same "architecture".
both versions are 32bit alright
suspect #2: the usual mismatch between msvcr90.dll (missing from the Gem distribution) and the likes. the mailinglist archives should cover this.
thanks, IOhannes. that was the right hint !
actually it was "pthreadVC.dll" in the BIN folder that caused the error. the self-compiled PD had its accompanying file "pthreadVC.lib" dated from 2002, whereas the .dll was from 2018. i figure here's the mismatch.
so i exchanged the new "pthreadVC.dll" with the old one from the official .zip package and Gem loaded and worked fine !
best
oliver
On 03.12.18 13:55, oliver wrote:
actually it was "pthreadVC.dll" in the BIN folder that caused the error. the self-compiled PD had its accompanying file "pthreadVC.lib" dated from 2002, whereas the .dll was from 2018. i figure here's the mismatch.
so i exchanged the new "pthreadVC.dll" with the old one from the official .zip package and Gem loaded and worked fine !
so which dll(s) did you remove, exchange,... exactly? (all this "new" and "old" and "official" kind of confuses me)
fgysdrm IOhannes
IOhannes m zmoelnig wrote:
On 03.12.18 13:55, oliver wrote:
actually it was "pthreadVC.dll" in the BIN folder that caused the error. the self-compiled PD had its accompanying file "pthreadVC.lib" dated from 2002, whereas the .dll was from 2018. i figure here's the mismatch.
so i exchanged the new "pthreadVC.dll" with the old one from the official .zip package and Gem loaded and worked fine !
so which dll(s) did you remove, exchange,... exactly? (all this "new" and "old" and "official" kind of confuses me)
hi, sorry for the confusion ...
so, we're talking windows (7/64bit) here:
the file i had to change in order to make Gem load on a self-compiled PD was "pthreadVC.dll".
after succesful compilation the "bin" folder contained "pthreadVC.dll" with a modified date of 03.12.2018, so i figure that this .dll was created during the compilation process.
i exchanged this "pthreadVC.dll" with a version that has a modified date of 03.04.2002. this file is included in the recent puredata .zip package from miller's site (pd 0.49)
after that action, Gem.dll loaded and worked alright. no other .dlls had to be changed.
best
oliver
-
IOhannes m zmoelnig -
oliver