Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: ted@loft.tnolan.com (Ted Nolan <tednolan>)
Newsgroups: comp.lang.tcl
Subject: Re: Where to put dll's in starkits
Date: 19 Jun 2025 19:25:28 GMT
Organization: loft
Lines: 28
Message-ID: <mbj6h8Fr16kU1@mid.individual.net>
References: <1031hr5$vka$1@dont-email.me> <1031ku9$1vhb$1@dont-email.me> <1031luu$2cum$1@dont-email.me> <1031mad$1vhb$2@dont-email.me>
X-Trace: individual.net HpgihXSm4mQcIOiBDiA3cASAXhWqHuaDUbBfLt0YdjtuTcyq64
X-Orig-Path: not-for-mail
Cancel-Lock: sha1:kLU2majsQFGwLKekuNUrbDqhpOw= sha256:9MMd/Ad+jZBiNzFpjx/wS5zWzQgEMfQ+ebPBBK+rmHw=
X-Newsreader: trn 4.0-test76 (Apr 2, 2001)

In article <1031mad$1vhb$2@dont-email.me>, saito  <saitology9@gmail.com> wrote:
>On 6/19/2025 2:46 PM, Robert Heller wrote:
>
>> 
>> OK, this is related to the Img package. It expcts some "system libraries" to
>> be installed. I guess someplace like C:\System32 (or whatever MS-Windows uses
>> for what Linux would call /usr/lib. I am not sure what the MS-Windows
>> libraries it needs are, but the Linux dependencies under Linux (Debian, arm64)
>> for libtk-img 1.4.14 include: libjpeg62-turbo, libpng16-16, and libtiff6.  I
>> believe these DLLs are readily available.
>> 
>> I don't really know what the proper way to deal with this under MS-Windows.
>> My only real thought would be to re-build tk-img staticly linked to these
>> graphics libraries.  (Under Linux these sorts of libraries are often pulled in
>> by various other graphics programs.)
>> 
>
>That's a good idea.

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".
-- 
columbiaclosings.com
What's not in Columbia anymore..