Hi Folks
I was having a heck of a time with iemlib on windows64 and i think i must have assumed it was pre-compiled Well, after fooling with a few times i compiled it for 64 bit and pd 50 Should i share the results to deken?
or is the expectation that people would compile their own versions? I also noted that one must load iemlb now as well at startup not just it's path
Should i share the results to deken?
Why? What is the problem with :
iemlibv1.22(Darwin-i386-32)(Linux-amd64-32)(Windows-amd64-32)(Windows-i386-32)(Sources).dek Uploaded by musil @ 2018-11-13 22:51:54
up on deken?
It works for me on win/pd 64bit :
~~
iemlib (1.22) library loaded! (c) Thomas Musil Nov 13 2018 : 21:27:10 musil@iem.atmailto:musil@iem.at iem KUG Graz Austria
~~
Note that this pkg has "iemlib.m_i386" (this is the 32bit dll) and "iemlib.m_amd64" (the 64bit dll).
Did the absence of .dll files had make you think that you needed to compile?
:)
Mensaje telepatico asistido por maquinas.
On 10/27/2019 8:08 PM, pat pagano wrote: Hi Folks
I was having a heck of a time with iemlib on windows64 and i think i must have assumed it was pre-compiled Well, after fooling with a few times i compiled it for 64 bit and pd 50 Should i share the results to deken?
or is the expectation that people would compile their own versions? I also noted that one must load iemlb now as well at startup not just it's path
-- Patrick Pagano B.S, M.F.A Assistant Professor, Interactive Media & Education Audio Projection & Performance Design Howard Community College Columbia, Maryland USA http://shreeswifty.github.io (352)226-2016
Pd-list@lists.iem.atmailto:Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 28.10.19 00:08, pat pagano wrote:
I also noted that one must load iemlb now as well at startup not just it's path
this has *always* been the behaviour if iemlib.
some people thought it nicer to only need to specify the path, and distributed binaries that did not require to load the "iemlib" libraries. but this was always done without the consent of the upstream author (tmusil), and now that the people who provided those binaries stopped doing so you only get upstream's preferred format.
the good news is, that there's no longer a(n arbitrary) distinction between "iemlib1" and "iemlib3" and ... and you simply have to load "iemlib" and add it's path. preferably via [declare -path iemlib -lib iemlib] instead of startup options.
gfdmsft IOhannes
-
IOhannes m zmoelnig -
Lucas Cordiviola -
pat pagano