Overview
Artifact ID: | 56d7f949575881f22eab00ac745825753050edf9 |
---|---|
Ticket: | f929fddcfc1cced456821d15ac44dcd863b4ff85
Tclkit generation problems |
User & Date: | rkeene on 2012-09-25 15:28:38 |
Changes
- Appended to comment:
<hr /><i>rkeene added on 2012-09-25 15:28:38 UTC:</i><br /> To whom it may concern, There is an issue with Metakit and Tcl trunk (8.6b3 was just released from trunk). I have not resolved it yet, but it will likely result in a new patch against metakit being added to kitcreator's list of metakit patches. In the mean-time you can indeed use zip- or cvfs-based storage. In zip-based storage there is a zip-file already appended to the exectuable that you need to update. You should be able to extract it using the "unzip" command, or update it using the "zip" command. For cvfs-based storage the base of the kit is stored in an internal archive that cannot be modified, but if you attach your source code in the form of a zip file appended to the end of the executable it will be picked up and used. That is, for CVFS: cd myapp.vfs zip -r ../myapp.zip * cd .. cat tclkit-using-cvfs myapp.zip > tclkit-with-myapp chmod +x tclkit-with-myapp Thanks, Roy Keene
- priority changed to: "High"
- severity changed to: "Important"
- subsystem changed to: "Mk4tcl"