[erlang-questions] Bundling C dependencies with a release
Tue Oct 25 17:39:08 CEST 2016
I don't know about best practices, but compiling the code and copying it to
the "priv" directory seems to work well. The pre_hooks in rebar are very
helpful for this. By using the priv dir, everything gets included as part
of the release, at least with rebar3. Just zip up or copy the "rel"
directory under _build and you're good to go.
Hope that helps.
On Tue, Oct 25, 2016 at 5:35 AM, Radu Popescu <i.radu.popescu@REDACTED>
> I'm developing an Erlang application which is structured as an OTP
> release. It contains OTP applications and some native executables (written
> in C++). One of the Erlang dependencies also requires libsodium.
> When the time will come to deploy this - mostly to RH and Ubuntu/Debian
> servers, the idea is to have something as self-contained as possible.
> Are there best practices for how to handle C library dependencies for an
> Erlang/OTP release? I appreciate any advice.
> Best regards,
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions