2 Commits

Author	SHA1	Message	Date
will.anderson	027ad82db2	fix elb linker: remove runtime imports from el-install, add --clean, catch in dev/stage CI ... el-install.el explicitly imported runtime/*.el modules (string, env, fs, exec, json, http), which elb compiled to .c files in the shared dist/bin out_dir. Linking those alongside el_runtime.c caused multiple definition errors for every runtime function (http_get, http_patch, etc.). The runtime .el files are thin wrappers over seed primitives already compiled into el_runtime.c — no import needed. Fixes: - Remove all explicit runtime imports from el-install.el (root cause) - Add --clean to every elb invocation in sdk-release.yaml so each build starts with a clean out_dir (defense-in-depth against stale .c files) - Add elb build + epm/el-install build steps to ci-dev.yaml and ci-stage.yaml so linker errors are caught on every PR, not just stage->main	2026-05-07 03:20:44 -05:00
Will Anderson	592f8f482a	add el-install binary and SDK bundle to release pipeline ... - lang/tools/install/el-install.el: El program that fetches the latest release from the Gitea API, downloads el-sdk-latest.tar.gz, and extracts it into ~/.el (or a custom prefix passed as argv[1]) - lang/tools/install/manifest.el: build manifest for the el-install package - .gitea/workflows/sdk-release.yaml: build elb, epm, and el-install binaries; bundle elc + elb + epm + runtime files into el-sdk-latest.tar.gz; attach both the tarball and el-install binary to the Gitea release alongside the existing per-file GCP uploads	2026-05-05 03:02:56 -05:00