2c18fcdc61
Release builds can legitimately want runtime dynamism (redefinition, eval,
load-string), so closed-world direct-linking shouldn't be forced on them. Gate it
behind an explicit --direct-link flag (or deps.edn :jolt/build {:direct-link
true}); off by default in every mode, including release and --opt.
build-binary takes an explicit direct-link? arg instead of deriving it from the
mode. build-smoke now covers the --direct-link path and asserts the cross-ns call
actually lowers to a jv$ binding; default release stays dynamically linked.
|
||
|---|---|---|
| .. | ||
| rfc | ||
| spec | ||
| building-and-deps.md | ||
| grammar.ebnf | ||
| host-interop.md | ||
| libraries.md | ||
| seed-overlay-registry.md | ||
| tools-deps.md | ||