I scripted a one-step build in Tcl using the instructions here: http://wiki.tcl.tk/11861
Here are some adjustments to the basic instructions (steps 1-6 of Tclkit):
Step 1. The .kit and Tclkit can be found at Google Code: https://code.google.com/p/tclkit
You will need three files: tclkitsh, tclkit and sdx-xxx.kit. The .exe file with the “sh” in the name lets you run Tclkit via the command-line, which is good for automation.
Windows may interfere with the downloaded files. Right-click on the files and Unblock them.
Step 2. You will use the non-sh .exe file in only one step: the last one, passed as an argument to -runtime. So there is no need to rename any file to “tclkit2.exe.”
Step 3. Use exec to launch the tclkitsh executable. For example,
exec [pwd]\\tclkitsh-8.5.9-win32.upx.exe sdx-20110317.kit \
Step 4. Nothing to note!
Step 5. Skipped.
Step 6. I referenced StackOverflow for this step: http://stackoverflow.com/questions/1379577/steps-to-create-a-tcl-starkit-on-a-windows-platform
First, do not use “bird.exe”; use “bird” as the argument. And for the -runtime parameter, specify the non-sh tclkit executable name. Finally, rename the file to .exe.
If you use bird.exe before the rename, Tclkit will output itself as a different name. If you double-click it, it will open Tclkit console. That’s how you’ll know to use “bird” instead.
If you specify the sh version of Tclkit to the -runtime param, you will get an Mkt4 error. You will need to pass in the non-sh version.
I’m saving up for ActiveState Pro Studio.