Static Erlang

Fred Hebert mononcqc@REDACTED
Mon Aug 3 15:21:02 CEST 2020

One of the things to figure out properly is to then make sure other
dependencies (i.e. openssl, wx libraries, etc.) are statically linked when
compiling the VM. I do not think that there is a full list of options put
in one place to choose to do that. For example,
will let you make sure that the libraries used are statically linked (when
combining with --with-ssl at least)

As far as I know, the SSL-specific switches exist to help with Windows
builds, but I'm not necessarily aware of similar options for other

On Mon, Aug 3, 2020 at 3:53 AM Roger Lipscombe <roger@REDACTED>

> On Mon, 3 Aug 2020 at 08:13, Grzegorz Junka <list1@REDACTED> wrote:
> > I am essentially looking for a way of deploying an Erlang release to a
> system that doesn't have Erlang installed (and doesn't support docker).
> You don't need static linking for this. Include the Erlang runtime in
> your release (relx does this by default). Why doesn't that work for
> your case?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the erlang-questions mailing list