<div dir="ltr">Consider statically linking libsodium to your native executable to eliminate the runtime dependency.<br><br><div class="gmail_quote"><div dir="ltr">On Tue, Oct 25, 2016 at 8:50 AM Radu Popescu <<a href="mailto:i.radu.popescu@gmail.com">i.radu.popescu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello!<br class="gmail_msg">
<br class="gmail_msg">
I'm developing an Erlang application which is structured as an OTP<br class="gmail_msg">
release. It contains OTP applications and some native executables<br class="gmail_msg">
(written in C++). One of the Erlang dependencies also requires libsodium.<br class="gmail_msg">
<br class="gmail_msg">
When the time will come to deploy this - mostly to RH and Ubuntu/Debian<br class="gmail_msg">
servers, the idea is to have something as self-contained as possible.<br class="gmail_msg">
<br class="gmail_msg">
Are there best practices for how to handle C library dependencies for an<br class="gmail_msg">
Erlang/OTP release? I appreciate any advice.<br class="gmail_msg">
<br class="gmail_msg">
Thanks!<br class="gmail_msg">
<br class="gmail_msg">
Best regards,<br class="gmail_msg">
Radu<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
erlang-questions mailing list<br class="gmail_msg">
<a href="mailto:erlang-questions@erlang.org" class="gmail_msg" target="_blank">erlang-questions@erlang.org</a><br class="gmail_msg">
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" class="gmail_msg" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br class="gmail_msg">
</blockquote></div></div>