"Martin v. Löwis" writes:
> It was too difficult to get right, plus nobody was interested in
> using the daily MSI files.
>
> At some point, it was broken for several months (IIRC), with nobody
> reporting that breakage. So when we noticed, we just turned the service
> off.
Sounds right - the da
>> You'll need to build release versions of Tcl/Tk/Tix.
>
> Yes, I saw a reference to that online, but I wasn't sure if that was the
> problem -- is the naming convention really that 'tcl85g.lib' is the debug
> lib!?
Yes; Tcl apparently follows Unix conventions here rather than Windows
convention
On Thu, Nov 26, 2009 at 09:54:35AM +0100, "Martin v. L?wis" wrote:
> > First, the script that finds & builds the external dependencies has two
> > minor problems.
> >
> > * it puts Tcl in tcl-8.*, and Tk in tk-8.*, but msi.py looks for them in
> >tcl8.* and tk8.* to grab the license text. I
> First, the script that finds & builds the external dependencies has two
> minor problems.
>
> * it puts Tcl in tcl-8.*, and Tk in tk-8.*, but msi.py looks for them in
>tcl8.* and tk8.* to grab the license text. I changed the glob strings
>appropriately and that seemed to work.
Not sur
Hi all,
I got an MSI build working on my WinXP VM just now, and I wanted to
touch base with whomever it is that is maintaining this (wonderful!)
set of scripts...
I ran into three problems, and I managed to figure out two of them; the third
wasn't fatal. Note, the diff of my fixed checkout is at
