How to choose Elixir + Erlang versions to install

I realized that I’m just guessing what all the version numbers mean — and there are a lot of them. I’m not sure if this is documented anywhere. (?) Here’s what I do on MacOS, which seems to work:

  1. Install asdf
$ brew install asdf
  1. Install the asdf plugins for Elixir and Erlang. (Is it necessary to do both? I think so.)
$ asdf plugin add elixir
$ asdf plugin add erlang
  1. Look at the Elixir versions available:
$ asdf list all elixir

  1. The version 1.14.0-otp-25 seems like the most recent production-ready one, so I install that:
$ asdf install elixir 1.14.0-otp-25
  1. Now I need to find a compatible Erlang version. (Am I correct here?)
$ asdf list all erlang


Cool, the number 25 matches otp-25 from the Elixir package, and although the 25 here theoretically refers to the Erlang version and the other refers just to OTP, I suspect the nomenclature is rather loose. So I install 25.1.1:

$ asdf install erlang 25.1.1

Excellent! I’m almost ready to get to work. I have just one more hour ahead of me:

  1. Try to write Elixir code in VS Code with the LSP.
  2. It’s broken. Try to debug my dev env unsuccessfully. Post a forum question. Learn that the LSP has an undocumented dependency on OTP < 25.
  3. Redo all the above steps with Erlang 24 and Elixir with otp-24.
  4. Test all of this, and it appears to work: My inference about Erlang 24 = top-24 might be correct.

This is the setup process for new Elixir devs. :smile: Did I miss some docs or sign-posts along the way that would have made this easier?

1 Like

Erlang is the language and OTP is the distribution of the standard library and tools. Think java and jdk. Elixir is buiilt on top of the OTP, think Scala. And the LSP is another layer up. Usually, the backward compatibility of both Erlang and Elixir is pretty good; but in the case of LSP, it is probably doing something more intimate than an average package to the core.

Isn’t it even worse if you want wxwidgets compiled in the asdf version of erlang? I usually use Windows which is just scoop install erlang elixir and was a little frustrated by how much harder it was setting it up with asdf on Linux.

Weren’t the ElixirLS issues with OTP 25 patched recently? It’s been working for me for at least a couple of weeks.

1 Like

On linux you don’t even need asdf. just old fashion ./configure; make; make install and you have OTP. If you are lazy, just use whatever the distribution provides. I always compile elixir myself. It is only a minute and it is a good sanity check of your Erlang environment.

1 Like

in asdf the version suffix in the elixir distribution is to tell you which erlang version it was compiled against. I don’t know if there is actually a difference between them, but I always make sure they are in the same major range.
I am not using VSCode, but Lunarvim and have no issues with elixir-lsp and erlang 25+

1 Like

It depends on the elixir release, but generally there can be compile time checks in elixir to make use of new OTP features if compiled against a specific version.

By default elixir is compiled with the lowest supported OTP version, so using one compiled with a more recent one might unlock additional optimizations.


I’d highly recommend not installing asdf via homebrew. I can dredge up the GitHub issues later but it causes many things to break when updating the version of asdf itself.



Ok, let’s describe it step by step:

  1. Although Elixir projects are not required to follow SemVer, they must follow the format outlined on SemVer 2.0 schema.
  2. x.y.z at the start is the version of Elixir
  3. -rc.x is a x release candidate for said version
  4. -otp-x is a precompiled Elixir release for x major Erlang version
  5. The release without otp part before install needs to be compiled first with already installed and officially supported Erlang version
  6. main is the name of git branch which means you can test more or less stable new features before they added to an official release

If you want to install latest Elixir together with latest supported Erlang and you are not interested in release candidates as well as unstable main branch then you need to select release with latest x.y.z version of Elixir and latest -otp-x version, currently 1.14.0-otp-25.


In Erlang it’s much easier as it does not have a precompilled releases for other languages.

  1. a.b or a.b.c or a.b.c.d at the start is the version of Erlang - here we do not have padded .0 except b
  2. -rcx is a x release candidate for said version
  3. master is the name of git branch which means you can test more or less stable new features before they added to an official Erlang/OTP release
  4. maint and maint-x are stable git branches based on previous work in master, see otp/ for more information

Again if you look for latest stable release for Elixir version -otp-25 you need to select latest a.b or a.b.c or a.b.c.d - currently it’s 25.1.1.

Compile from source

If you want to compile Elixir on your own and you want to know which Erlang versions are supported then you can take a look at other releases or the documentation: Compatibility and Deprecations — Elixir 1.14.0 and Compatibility and Deprecations — Elixir v1.15.0-dev (main branch)

Erlang prebuild releases

There are prebuilt packages for Ubuntu LTS releases, see:

  1. michallepicki/asdf-erlang-prebuilt-ubuntu-18.04
  2. michallepicki/asdf-erlang-prebuilt-ubuntu-20.04
  3. michallepicki/asdf-erlang-prebuilt-ubuntu-22.04

There is also an open issue to officially support prebuilt packages in asdf-erlang repository, see: Support for precompiled binaries? asdf-vm/asdf-erlang#165

That’s all important things about Elixir and Erlang in asdf-based environment. Unfortunately I’m not MacOS user, so I don’t have any information specific to this OS.