I'm trying to get iemlib innto vanilla Win10 64 and Linux 64.
Deken provides the sources only.
Latest version in Deken is 1.22
On the IEM site latest is 1.17 latest.

Do I have to compile it? Could you give me a hint how?

@lacuna Did you try the one you want.?
I have seen that often is says "sources" but it is already compiled....... and I am using Windows.... but Win7 and 64 bit Pd.
For Linux the compilation (if necessary) should be "easy"....?
David.

@whale-av yes, I tried both from Deken (1.21 and 1.22) and 1.17 from the iem site.

On Windows10
the t3 objects are missing, those that I need.
The helpfiles are there. But the actual objects are missing...

now checked 1.16 from iem site and there is a /lib folder inside the /iemlib folder with iem_t3_lib.dll
But still doesnt work. And no t3 object .pd files ...

@lacuna Yes....... iemlib 1.17 is from November 2016 so little chance of compilation for 64-bit.

@whale-av does t3_delay-help.pd work on your machine?

@lacuna works on my Win10 64 installation. It looks like I had to list iemlib as a library to load on startup in order to get all the objects to be available, maybe try that?

@lacuna There you both have me stumped.
The object will not even create for me in Extended with the library declared.
The other t3_ objects are fine.

@whale-av @jameslo
now [declare -lib iemlib] made it with 1.22 from Deken on Win10
sorry for the false alarm! and thank you *

I've always been unclear why some libs needed to be loaded and others not--can you explain?

@jameslo Pd assigns separate binaries a namespace when an object has been created in a patch.
It doesn't need to search for them again for another creation. You will see a success in the log without a search on the second creation.
Most externals find their separate binaries when the object is created by a search for the name of the binary (it has the same name) in the search paths.

But some libraries have a single binary pack that contains many externals and so they have to be loaded at startup when all the namespaces for their externals are declared. Then when an object from that single binary pack is created it can be found. Otherwise creation fails because the name cannot be found by a search.
Some libraries contain both a single binary pack and multiple separate binaries.
More here........ http://msp.ucsd.edu/Pd_documentation/x4.htm
David.