Deutsch   English   Français   Italiano  
<1031ku9$1vhb$1@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: saito <saitology9@gmail.com>
Newsgroups: comp.lang.tcl
Subject: Re: Where to put dll's in starkits
Date: Thu, 19 Jun 2025 14:29:28 -0400
Organization: A noiseless patient Spider
Lines: 25
Message-ID: <1031ku9$1vhb$1@dont-email.me>
References: <1031hr5$vka$1@dont-email.me> <1031iqv$1fo4$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 19 Jun 2025 20:29:30 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="8a1c5b67116dfc35af9c07eeb581040b";
	logging-data="65067"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19xdslTpXurxg6LKUiTpEVB"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:nkC1b2qdvP6KvtH20bPGRrWIUEc=
Content-Language: en-US
In-Reply-To: <1031iqv$1fo4$1@dont-email.me>

On 6/19/2025 1:53 PM, Robert Heller wrote:
> Needing to put dlls in "bin" under MS-Windows is specific to MS-Windows, when
> the dlls are searched for and loaded my MS-Windows itself and I think only
> applied to Tcl itself being in a dll (shared library).  A starkit includes a
> staticly build Tcl interpreter.  Tk is still a shared library (dll), but this
> is loaded by Tcl using the load command.
> 
> There should not be any reason to to have a "bin" folder.  I think all dlls
> should go somewhere under lib.
> 

I wasn't suggesting that it should. The "bin" refers to "bin" under the 
main, full Tcl/Tk installation.  There I see a bunch of dll's some of 
whose names suggest they may be related to image processing.


> Do you have a specific package or set of dlls that are handled differently?
> 

I was trying to create a starkit with image related packages. I can't 
get svg support for example. I have included all packages related to img 
including tksvg. They are present in the vfs lib folder. jpeg is also 
problematic. It seems like they need some dll's beyond what is included 
in their "package" folders.