Re: Where to put dll's in starkits

Starkits re-define load to take care of shared libraries (.dlls, .so, etc.)
and will copy them to someplace like /tmp and then calling the original load
command to load them via libdl (or the MS-Windows equivalent).  That is,
shared libraries management is "transparent" and there is no need for special
code in the application itself -- eg one just uses a 'package require ' and it
just works properly.

At Thu, 19 Jun 2025 17:50:37 -0400 saito <saitology9@gmail.com> wrote:

 
On 6/19/2025 3:25 PM, Ted Nolan <tednolan> wrote:

 
It's been a while since I've done anything with Windows, but I seem
to recall that when I was trying to deal with a DLL bundled in a
"freewrap" application, that my startup code had to extract the DLL
to the "real" filesystem and either make sure it went to something
searched in the Windows "PATH" ("Path") or add that directory to the
Windows "PATH".

 
I believe this is true. Earlier I had set tcl's own auto_path which
sometimes helps.
 
At this point I am convinced it is a silly mistake on my part.
                                       
 

--
Robert Heller             -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software        -- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
heller@deepsoft.com       -- Webhosting Services