[erlang-questions] Releases and Different OSs

Tristan Sloughter <>
Wed May 18 15:22:59 CEST 2016

Right, we have a small section in the docs about doing this:
Tristan Sloughter

On Tue, May 17, 2016, at 08:05 PM, Vincent A Okonkwo wrote:
> Yes, that's what I meant.
> On Wed, May 18, 2016 at 12:58 AM Andrew Berman
> <> wrote:
>> So you're saying to download a binary of Erlang compiled on Linux and
>> put it on my Mac and then have it include that when building the
>> release tar?
>> On Tue, May 17, 2016 at 5:55 PM Vincent A Okonkwo
>> <> wrote:
>>> Hi Andrew,
>>> Been awhile since I tried this but if you are using relx there is a
>>> --include-erts=$PATH_TO_EXTRACTED_LINUX_ERTS ( {include_erts,
>>> $PATH_TO_EXTRACTED_LINUX_ERTS} for rebar) that you can use
>>> On Wed, May 18, 2016 at 12:42 AM Andrew Berman <>
>>> wrote:
>>>> Hi List,
>>>> So today I tried to create a release using rebar3 from my Mac and
>>>> deploy it to a CentOS box.  Everything works when I do not include
>>>> ERTS (and have Erlang installed on the target), but if I do include
>>>> ERTS, things fail (can't run run_erl), I'm assuming because the Mac
>>>> version of Erlang can't be run on CentOS, which makes sense.  So, I
>>>> wanted to know how people do deployments of their Erlang releases.
>>>> Do you set up boxes with each OS that matches your target OS and
>>>> compile on there, including ERTS in the release?  Do you not
>>>> include ERTS and make sure that all your Erlang installs are the
>>>> exact same version?   Just trying to figure out a good workflow.
>>>> Thanks for any advice!
>>>> Andrew
>>>> _______________________________________________
>>>>  erlang-questions mailing list
>>>> http://erlang.org/mailman/listinfo/erlang-questions
> _________________________________________________
> erlang-questions mailing list
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160518/e730e0af/attachment.htm>

More information about the erlang-questions mailing list