From: MartinLemburg on
Hello,

I just included a relative current version of tclxml, tcldom etc into
a starpack, but the way to this was cruel.

The dependencies of the DLLs and the right sequence of loading the
packages made some headaches.
Even if the "problem" is "solved" (it's more a work around), I still
would like to include something simple, so that my manipulations in
loading the depended DLL files (etc) can be removed again.

Is the a one DLL file, many tcl files solution or simply a KIT file
solution around?

So I could remove e.g. the temporary copying of the DLL files!

Thanks for any hint, suggestion, and so on!

Best regards,

Martin
From: Steve Ball on
Hi Martin,

I use Starkits and starpacks to distribute my own applications, so I
was feeling your pain ;-)

The good news is that this problem is solved with the to-be-released-
one-day v3.3 of TclXML. v3.3 rolls everything into a single library
and statically links the libxml2 and libxslt libraries.

Alas, I haven't been able to find the time to do the release
engineering necessary to make this public. Contact me by email to get
hold of the v3.3 package.

Alternatively, I could make a starkit of the PPDE application (only
starpacks are currently available) and you could download that and
unpack it to find the TclXML v3.3 binary package (the Mac OS X version
is already easily opened to get at the frameworks).

HTHs,
Steve Ball

On Jan 11, 10:54 pm, "MartinLemburg(a)Siemens-PLM"
<martin.lemburg.siemens-...(a)gmx.net> wrote:
> Hello,
>
> I just included a relative current version of tclxml, tcldom etc into
> a starpack, but the way to this was cruel.
>
> The dependencies of the DLLs and the right sequence of loading the
> packages made some headaches.
> Even if the "problem" is "solved" (it's more a work around), I still
> would like to include something simple, so that my manipulations in
> loading the depended DLL files (etc) can be removed again.
>
> Is the a one DLL file, many tcl files solution or simply a KIT file
> solution around?
>
> So I could remove e.g. the temporary copying of the DLL files!
>
> Thanks for any hint, suggestion, and so on!
>
> Best regards,
>
> Martin