From bd2dadab2d53cd341caf886ecd8541c5958f9546 Mon Sep 17 00:00:00 2001 From: griffin Date: Sat, 25 May 2024 18:32:05 +0000 Subject: Add note about static vs dynamic builds. --- doc/zipfs.n | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/zipfs.n b/doc/zipfs.n index d4f97a8..60b98c5 100644 --- a/doc/zipfs.n +++ b/doc/zipfs.n @@ -203,6 +203,18 @@ then the resulting image is an executable that will \fBsource\fR the script in that \fBmain.tcl\fR after mounting the ZIP archive, and will \fBexit\fR once that script has been executed. .PP +\fBNote:\fR \fBtclsh\fR and \fBwish\fR can be built using either +dynamic binding or static binding of the core implemenation +libraries. With a dynamic binding, the base application Tcl_Library +contents are attached to the \fBlibtcl\fR and \fBlibtk\fR shared +library, respectively. With a static binding, the Tcl_Library +contents, etc., are attached to the application, \fBtclsh\fR or +\fBwish\fR. When using \fBmkimg\fR with a staticly built tclsh, it is +the user's responsibility to preserve the attached archive by first +extracting it to a temporary location, and then add whatever +additional files desired, before creating and attaching the new +archive to the new application. +.PP \fBCaution:\fR highly experimental, not usable on Android, only partially tested on Linux and Windows. .RE -- cgit v0.12