-
Notifications
You must be signed in to change notification settings - Fork 19
Open
Description
On FreeBSD now all is well done. Kitgen created all binaries and I could build the sha256c.so for FreeBSD and cross-compile on my Linux host a FreeBSD runtime executable of my software project with the tclkit.
Only little patches were needed. Do you mind if I open a new page on https://github.com/patthoyts/kitgen/wiki:
How to create tclkits on FreeBSD
as a redux for my porting activity?
And I would like to suggest a little patch for the README file:
diff --git a/README b/README
index 5cc38cb..e6aa0fc 100644
--- a/README
+++ b/README
@@ -162,8 +162,10 @@ The remaining arguments of config.sh specify one or more build options:
* `mk` - build executables using Metakit instead of vlerq
When not specified, the default is to build all `cli`, `dyn`, `gui` variants.
+
If you ask for Metakit executables then these are in addition to the vlerq
-binaries. That is you will get both tclkit-cli and tclkitsh.
+binaries. That is you will get both binaries: the vlerq based tclkit-cli and and the Metakit
+based tclkitsh.
Makefile
Critcl needs the Metakit extension and I went wrong all the time by trying to use tclkit-cli critcl.kit ...
Metadata
Metadata
Assignees
Labels
No labels