On Apr 29, 2011, at 9:02 AM, august wrote:
Windows and Mac OS X both use the path of the executable for finding other dlls, but not the path of each dll that is loaded (that could be a lot of paths). I think GNU/Linux might do the same, I don't remember off the top of my head, but you so rarely encounter this on GNU/Linux since you're almost always installing dlls in the path (/usr/lib, /usr/local/lib).
With the Mac version of readanysf~, the libraries are loaded from a statically defined path (/Library/Pd/readanysf~). So to make an easily deployable readanysf~ for Windows, this issue will have to be sorted out.
Any suggestion on how to do that Hans? Is there a way to make it so that it tightly integrates with Pd-extended?
That part of Windows linking I don't know, so the thing to do is to
find whether there is a way to add to the DLL load path, then make
readanysf~ do that. That's probably a single function call.
Otherwise, people will need to install the DLLs into pd\bin or \Windows
\system32.
.hc
As we enjoy great advantages from inventions of others, we should be
glad of an opportunity to serve others by any invention of ours; and
this we should do freely and generously. - Benjamin Franklin