jn
/
punkshell
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
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.
1038 Commits
1 Branch
1 Tag
191 MiB
 
 
 
 
 
 
Tree: 50a74bc124
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '50a74bc124'
${ noResults }
punkshell/src/runtime
Julian Noble 7279067976
mapvfs.config: restore punk86 kit mapping on the 8.6.17 dyn tclkit 		1 week ago
..
AGENTS.md AGENTS.md with DOX framework 1 month ago
Readme.md misc scriptapps and file/folder organisation 10 months ago
mapvfs.config mapvfs.config: restore punk86 kit mapping on the 8.6.17 dyn tclkit 1 week ago
punk1.ico far too big a checkin. vfs folders that will need to be optimised later etc 2 years ago
tclkit.ico far too big a checkin. vfs folders that will need to be optimised later etc 2 years ago
vendorlib_vfs.toml punk905_beta promoted to punk905 (trial accepted) 1 week 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.