Skip to main content
Version: kirkstone

Contributing with meta-erlang

To develop the meta-erlang layer, you need to setup the Yocto project environment and starting to make changes in meta-erlang code.

Add a new erlang version​

When Erlang OTP team releases a new version, and you wish to try that version with meta-erlang then you can do the follow steps:

Run the manifest script to create the bitbake files:

scripts/contrib/erlang/generate-manifest --erlang-version 21.3.2 > recipes-devtools/erlang/erlang-21.3.2-manifest.inc

Copy the erlang recipe to the new version:

cp recipes-devtools/erlang/erlang_21.1.0.bb recipes-devtools/erlang/erlang_21.3.2.bb

Create include file to hold the SRCREV and point to the git sha1 commit that represents the Erlang OTP version:

echo 'SRCREV = "7e6fff1e849998a3dd747b4d3cf35f39cb896aa0"' >> recipes-devtools/erlang/erlang-21.3.2.inc

Add a new elixir version​

Copy the elixir recipe to the new version:

cp recipes-devtools/elixir/elixir_1.8.2.bb recipes-devtools/elixir/elixir_1.9.0.bb

Open the elixir_1.9.0.bb and change the following:

  • SRCREV: must point to the sha1 commit that represents the new elixir version
  • SRC_URL: change the version ('branch=') to the base elixir version branch. Example: 'v1.8'