Dear all, Tcl/Tk on MacOS challenges me:
Let us talk about our experience and best practices.
Manfred
TR: my experience:
Otherwise, make sure to check the New Tcl/TkAqua FAQ (and yes, it needs an update!)
ManfredR - 2025-01-10 21:55:20
I tried to codesign "vanillawish","tclkit" and a single "wish" and "tclsh". my observation:
I fear this observation is based on, that codesign does not sign binaries with a payload. If this is the case "vanillawish" and "tclkit" are no oportunity to provide a tcl-runtime with batteries included for MacOS apps.
ALX I assume that all files embedded into the VFS must be code-signed first. Afterwards, the executable needs to be signed.
ManfredR - 2025-01-29 15:00:00
I found an approach used to build tkChat for MacOS:
and a manual
This approach requires wish.app as template
wish.app/ Contents/ Info.plist Frameworks/ Tcl.framework/ Tk.framework/ MacOS/ wish Resources/ wish.icns
to use this template with the name myApp all whish should be renamed to e.g. myApp
myApp.app/ Contents/ Info.plist Frameworks/ Tcl.framework/ Tk.framework/ MacOS/ myApp Resources/ myApp.icns
... and if I got it right:
./myApp.app/Contents/MacOS/myApp
is a nearly native
wish
looking for a tcl-script
./myApp.app/Resources/Scripts/AppMain.tcl (or main.tcl???)
my Question:
... is there anybody out there, providing a wish.app as a template (for tcl 8.6)?