You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Julian Noble 145e785c42 commandstack 0.5.0: help overview + PUNKARGS docs; first characterisation suite 1 week ago
..
assets/logo
bin
bootsupport promotion outputs: punk::libunknown 0.2.4 into bootsupport + _vfscommon.vfs 1 week ago
buildsuites
decktemplates
defaultconfigs
doc
embedded
lib
lib_tcl8
lib_tcl9
modules commandstack 0.5.0: help overview + PUNKARGS docs; first characterisation suite 1 week ago
modules_tcl8
modules_tcl9
project_layouts G-032 ACHIEVED 2026-08-03: launcher help + parsed subcommands (core 0.3.0, 0.48.0) 1 week ago
runtime
scriptapps retire src/scriptapps/punk.tcl (stale pre-G-155 _build dev-launch shim) 1 week ago
testansi
testdata
tests commandstack 0.5.0: help overview + PUNKARGS docs; first characterisation suite 1 week ago
text
tools
vendorlib kettle tilde fix: punk::mix::cli 0.6.1 + vendored kettle app.tcl local patch (tcl9) 1 week ago
vendorlib_tcl8
vendorlib_tcl9
vendormodules G-111: modpod 0.1.6 tidy + first test baseline (0.47.2) 1 week ago
vendormodules_tcl8
vendormodules_tcl9
vfs promotion outputs: punk::libunknown 0.2.4 into bootsupport + _vfscommon.vfs 1 week ago
AGENTS.md
README.md
Tcl9icon.six
Tcl9icon.svg
build.cmd
build.ps1
build.tcl
error_overtype.txt
make.tcl G-025 landed + G-031 moduledoc: buildinfo self-report (stamp/live/source/runtime-record) + runtime-queryable boot-core API doc (0.47.0) 1 week ago
test.txt

README.md

punk shell

Runtimes

#run from project root:  
./bin/punk-runtime.cmd list -remote
# This is a cross-platform polyglot wrapper that should run from bash, or with tclsh or in windows directly in powershell/cmd.exe
./bin/punk-runtime.cmd fetch

#if no retrievable runtime for your platform, you'll need a vfs capable tclkit or a zipfs capable tclsh with an attached vfs

#todo: exact notes on creating suitable runtimes (plain tclsh will likely be missing zipfs vfs to mount)

Make Instructions (mint / promote / bake)

  • Use tclsh|<punkruntime> make.tcl <commandname> to mint .tm modules and rebake the punk executables In normal use it should be called from the project root. e.g
 tclsh src/make.tcl vendorupdate   ;# if needed

 tclsh src/make.tcl packages       ;# mint the libs / modules from src to <projectroot> (version-stamped)
 # or separately:
 # tclsh src/make.tcl modules      ;# src/modules -> /modules (etc)
 # tclsh src/make.tcl libs         ;# src/lib     -> /lib (etc)

 tclsh src/make.tcl vfscommonupdate ;copy the  libs/modules that are now in <projectroot>/modules to vfs system for inclusion in the binary.

 # If make.tcl dependencies are modified:
 # tclsh src/make.tcl bootsupport  ;# src/modules -> src/bootsupport/modules,  src/lib -> src/bootsupport/lib (etc)

 tclsh src/make.tcl bake            ;# assemble kit/zipkit executables from the promoted vfs payload + runtimes
 # (consumer path from a CLEAN checkout: 'tclsh src/make.tcl bakehouse' = packages + bake in one run;
 #  'make.tcl workflow' prints the full data-flow overview.)
A common interactive test scenario (after running src/tests/runtests.tcl to test the unversioned source)
is to run 'tclsh src/make.tcl modules'
Then '<punkexecutable> dev'
This will source modules/libs from <projectroot>/modules and <projectroot>/lib intead of from the executable's vfs. 
  • Then Use tclsh|punk build.tcl to run the 'kettle' system to build doc files,
    or - use the pmix KettleShell command from within the punk shell to perform kettle operations. Confirm with user or ask user to manually run.

(The name 'build.tcl' is the standard name used by the Kettle system - it is not for building the punk project.)