Mon Aug 3 02:14:21 CEST 2020
Any C program can be compiled statically unless it relies on some dynamic
loading as part of its work.
The Problem is that *erl *and few other small tool programs are launching
`beam.smp` as a part of operation, and compiling each of them statically
will result in a pile of multi-megabyte executables.
On Mon, 3 Aug 2020 at 01:13, Grzegorz Junka <list1@REDACTED> wrote:
> Is it possible to compile Erlang Beam statically so that when I am doing
> a release it doesn't require any dynamically loaded libraries on the
> host to which the release is being deployed? I was trying the various
> configure options but the compilation was failing (for various reasons,
> mostly missing or conflicting function signatures). I could try again
> and post exact errors but would prefer to start with a tried and tested
> set of options.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions