Prev: Where is IWidgets?
Next: Mouse over
From: Larry W. Virden on 24 Mar 2010 07:40 On Mar 23, 8:06 am, Helmut Giese <hgi...(a)ratiosoft.com> wrote: > Possible solutions are > - static linking of 3rdparty.dll into ext.dll, which may not be > possible if you don't have sources, > - putting 3rdparty.dll into a place where Windows will surely find it > - but you may not have the priviliges to do so. > > Is there a way to solve this? Any idea will be greatly appreciated. My first thought was including the 3rdparty.dll as one of the files distributed in the same directory as ext.dll - but of course, you have to have the legal right to do that. The problem with most of the "extend the path" or "use function to point to" is that if you don't control where the 3rdparty.dll is (via distribution), then finding it programatically may be a tough job. I mean, during the install process you could through some process look to see what dlls the system knows about, then, if there are ones not available in the standard locations, prompt the user for a series of paths, then store that information in a location to use at runtime.
From: Helmut Giese on 25 Mar 2010 09:10 Hi, thanks to all of you. Info tugged away for further reference. Actually, for once this posting was not about a question _I_ had at the moment. There is this thread Building tkpng package which is now almost 2 weeks old but which kind of kept going on. After my last post there I figured "Surely the OP's next question will be: Ok, I found that tkpng.dll depends on xyz.dll - how can I arrange for xyz.dll to be loaded?" and didn't know the answer off hand. So in anticipation of this hypothetic question I posted it before it actually occurred - which so far hasn't happened. Seems like I should send my crystal ball to maintenance ... Best regards Helmut Giese
From: Spam on 25 Mar 2010 13:13
On Thu, 25 Mar 2010, Helmut Giese (in a fit of clairvoyance) wrote: > > Hi, > thanks to all of you. Info tugged away for further reference. > Actually, for once this posting was not about a question _I_ had at > the moment. > There is this thread > Building tkpng package > which is now almost 2 weeks old but which kind of kept going on. After > my last post there I figured > > "Surely the OP's next question will be: Ok, I found that tkpng.dll > depends on xyz.dll - how can I arrange for xyz.dll to be loaded?" > > and didn't know the answer off hand. So in anticipation of this > hypothetic question I posted it before it actually occurred - which so > far hasn't happened. > > Seems like I should send my crystal ball to maintenance ... > Best regards > Helmut Giese They don't call it .DLL hell for nothing! Cheers, Rob Sciuk |