[erlang-questions] Elixir from Erlang

Oliver Korpilla Oliver.Korpilla@REDACTED
Fri Mar 1 15:49:27 CET 2019


In our project we use mix as the central build tool, pulling in both Erlang and elixir dependencies.

Experience is generally good with just a rather minor gripes: 
* It looks like some step has to always be redone for our rebar3 dependencies. syn and ibrowse are always listed as being rebuilt but always finish quickly.
* It was tricky to use dependencies from local share and building without connecting to the internet. (Not allowed in our build process for reproducibility reasons.)

So, our configuration based on mix/hex/distillery has been great for delivering a packaged release but I won't deny it has a few quirks of its own. Since we use asn1ct, syn, and ibrowse we have plenty of pure Erlang code in the mix (pardon the pun) and I could imagine using the same for a pure Erlang project, too.


Gesendet: Freitag, 01. März 2019 um 15:18 Uhr
Von: "Roger Lipscombe" <roger@REDACTED>
An: "Igor Clark" <igor.clark@REDACTED>
Cc: erlang-questions <erlang-questions@REDACTED>
Betreff: Re: [erlang-questions] Elixir from Erlang
On Fri, 1 Mar 2019 at 10:26, Igor Clark <igor.clark@REDACTED> wrote:
> Is that right, or am I missing something? Is there a way to do this? Are there language-level reasons or extensions which mean this isn’t possible anyway? If not, what would be involved? Would it be possible for rebar3 to support this, so that erlang projects could just include elixir libraries as deps?

Or you could use mix for compiling your Erlang project, at which point
you get access to both sets of deps. Note, however, that there's an
outstanding problem with running eunit tests from mix that we never
managed to nail down properly.

Or or you could compile your project with erlang.mk, which also
supports hex.pm dependencies and can compile Elixir with a plugin.
erlang-questions mailing list

More information about the erlang-questions mailing list