Mon Aug 3 09:03:27 CEST 2020
Not sure what you mean. Of course any C program can be compiled
statically. I am just looking for the right options. Are you saying
beam.smp can't or shouldn't because it's being launched as part of
"operation"? It shouldn't matter since beam.smp isn't a library but an
executable. And as far as a release goes it should be launched once then
be available to any tool or script through a shell or network connection.
On 03/08/2020 01:14, Dmytro Lytovchenko wrote:
> 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
> <mailto:list1@REDACTED>> wrote:
> Is it possible to compile Erlang Beam statically so that when I am
> 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
> mostly missing or conflicting function signatures). I could try again
> and post exact errors but would prefer to start with a tried and
> set of options.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions