This layer provides support for Erlang and Elixir for use with OpenEmbedded and/or the Yocto Project build system:
See meta-erlang documentation.
This layer depends on:
URI: git://git.openembedded.org/bitbake branch: master
URI: git://github.com/openembedded/oe-core.git branch: master revision: HEAD
URI: git://git.openembedded.org/openembedded-core layers: meta branch: master
For erlang odbc:
URI: https://github.com/openembedded/meta-openembedded.git layers: meta-oe branch: master
For erlang lksctp run-time support:
URI: https://github.com/openembedded/meta-openembedded.git layers: meta-networking branch: master
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-erlang]' in the subject'
When sending single patches, please using something like:
git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-erlang][PATCH
Interim layer maintainer: João Henrique Freitas joaohf@gmail.com
Use the bitbake-layers add-layer command to add the meta-erlang to the configuration file:
cd ~/poky/build
bitbake-layers add-layer ../meta-erlang
Then run:
bitbake erlang-embedded-image-minimal
That will create an image with embedded erlang.
Or add IMAGE_INSTALL_append = " erlang" in conf/local.conf file and run
bitbake core-image-minimal to get an image with erlang support.
Also, there are a set of recipe examples demonstrating how to integrate Erlang/Elixir projects into YP/OE. The examples tried to cover some common use cases when dealing with cross compiled applications.
meta-erlang tries to support a well balanced range of Erlang, Elixir and Yocto Project versions. The purpose is to provide up-to-date recipes following the latest fixes found in Erlang and Elixir projects as well keeping the old recipes to not break compatibility.
As meta-erlang provides multiple versions for the same recipes, pay attention to configure the variable PREFERRED_VERSION in one of the configuration file like local.conf, site.conf, auto.conf or distro/include files. Like this:
PREFERRED_VERSION_erlang = "23.1.3"
PREFERRED_VERSION_erlang-native = "23.1.3"
PREFERRED_VERSION_elixir = "1.10.0"
PREFERRED_VERSION_elixir-native = "1.10.0"
However if you have any specific requirements for a special recipe version, you can always add it in your application/middleware layer.
Following the OTP Versions Tree, Elixir Compatibility and Deprecations and Yocto Project releases meta-erlang supports the below versions:
Erlang:
Elixir:
Yocto:
meta-erlang provides specific branches for each YP/OE release. So, please stick with one of the supported branches to avoid compatible probles:
Even though supporting a range of versions, users are recommended to checkout specific meta-erlang branch in order to find out the correct combination between Erlang/OTP versions. Due to how Erlang/OTP and YP/OE are made, it is not possible always to keep some versions without backporting or fixing cross compilation issues.
This layer can provide the entire Erlang installation, from the base runtime (erlang) to a full erlang development environment with all of the bells and whistles (erlang-modules).
A list of all the packages provided can be found in the manifest file, at recipes-devtools/erlang/erlang-${PV}-manifest.inc. This file needs to be re-generated and new SRCREVs need to be added whenever the version hanges.