Dne úterý 31. října 2017 22:45:57 UTC+1 Rich napsal(a):
>
> Or, maybe the windows dll loading API is more restrictive filename
> character wise than other parts of windows (note, just a guess here).
Hmm, maybe windows cant load DLL from that path with special cahrs - but that doesn't matter, because as far as i know (and maybe im wrong) starpack always copy DLLs from starkit vfs to some TEMP folder in windows.
I created workaround and for each binary package im now using my own loader which copy DLLs to temp and then loads them to app.
If anyone interested, im using this proc:
proc setup_dll {dir ver} {
set tmpdir [file join $::env(TEMP) myapp]
file mkdir $tmpdir
foreach sdll [glob -nocomplain -directory $dir -tails *.dll] {
catch {file delete -force $tmpdir/$sdll}
catch {file copy -force $dir/$sdll $tmpdir/$sdll}
load [file join $tmpdir $sdll] $ver
}
}
and then in pkgIndex, im doing this:
package ifneeded tls 1.6.5 \
"[list source [file join $dir tls.tcl]] ; \
[list setup_dll $dir tls];"
And it works :)
But i would like to find bug in starkit and report it. Can anyone point me, where in the startkit ecosystem is done DLL copying?
I looked into
starkit-1.3.3.tm, but found nothing interesting...