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 47c9f99eff G-057 achieved: flip, archive record, reference sweep, owning-doc pointers 2 days ago
..
AGENTS.md G-057 achieved: flip, archive record, reference sweep, owning-doc pointers 2 days ago
Readme.md
mapvfs.config G-133: bake payload/target consistency checks - advisory arch scan + smoke-require probe 4 days ago
punkshell.ico Project icon: punk1.ico -> punkshell.ico, artwork from the src/assets/logo master 3 days ago
punkshell.ico.assetorigin.toml G-135: platform-neutral icon generator + per-asset assetorigin sidecars 2 days ago
tclkit.ico
vendorlib_vfs.toml contextual sweep: deprecated make.tcl subcommand references (user-directed, incl. contract lines) 6 days ago

Readme.md

Use mapvfs.config to configure building of a kit (metakit or zipfs) executable from customized .vfs folders within src/vfs

A runtime must be installed in the appropriate bin/runtime/ folder to build the executable. These can be installed by running: bin/runtime.cmd fetch or alternatively by downloading from an artifact source such as : https://www.gitea1.intx.com.au/jn/punkbin

Appropriate runtimes should be self-contained Tcl executables that are either metakit or zipfs aware, and have an attached vfs with 'info library' support files.

A plain tclsh, even if it has zipfs support, is unlikely to work unless it has the tcl_library folder (with init.tcl and others) and possibly some other required modules such as msgcat placed within the .vfs folder being used to build the executable.

A plain tclsh may commonly depend on shared libraries elsewhere on the system, and so the resulting executable may not be as portable.