18 posts tagged with "meta-erlang"

Gleam is a new language that runs on Erlang VM. As one the aims of meta-erlang layer is to offer support to BEAM ecosystem in YP/OE ecosystem gleam support has been added to meta-erlang.

I'm not a gleam programming. Actually, I recently discovered gleam (and its purposes). And I'm still learning it. After watching the talk Keynote: Gleam's Journey on the BEAM - Hayleigh Thompson & Louis Pilfold at Code BEAM Europe 2024, I give a try and add it to meta-erlang layer.

ptest (package test) means packaging and installing runtime tests that are included in many upstream packages. At the end of the day it runs Erlang/OTP cross compiled test suite on the target hardware. The aim is to detect a range of problems when running test suites on different combinations of architecture processors and libc.

Usually, when designing a linux distribution using YP/OE we want a slim image with only what we need to run a specific application (or applications). In this post we'll discuss a bit about erlang and elixir packages that meta-erlang layer provides.

It's important to know how the packages are divided into smaller ones in order to offer a better composition when creating linux distributions with YP/OE.

This blog post is a tutorial about how to make A/B software updates with fwup tool and Yocto Project.

We've added support for the following new Erlang/OTP releases:

And the following Elixir releases:

I was planing to also add Erlang/OTP 27.0 to LTS kirkstone release. However it is not feasible as Erlang/OTP 27 uses autoconf 2.72 and kirkstone uses 2.71. Thus, there is an incompatible related to build system.

Intro​

From livebook.dev website:

Automate code & data workflows with interactive notebooks.

Livebook is getting famous for modern notebooks. It helps a lot for several tasks and to solve issues where documentation and code have to walk together.

We've added support for the following new Erlang/OTP releases:

We've added support for the following new Erlang/OTP releases:

We've added support for the following new Erlang/OTP releases:

In additional to those new versions, now it's possible to read Erlang/OTP documentation in Erlang shell. The docs .chunk files get generated during build time and one could easily install it by adding the package erlang-modules-dev.

Intro​

From atomvm.net website, atomvm is:

AtomVM is a lightweight implementation of the the Bogdan Erlang Abstract Machine (aka, the BEAM), a virtual machine that can execute byte-code instructions compiled from Erlang or Elixir source code. AtomVM supports a limited but functional subset of the BEAM opcodes, and also includes a small subset of the Erlang/OTP standard libraries, all optimized to run on tiny micro-controllers. With AtomVM, you can write your IoT applications in a functional programming language, using a modern actor-based concurrency model, making them vastly easier to write and understand!

One of the atomvm goals is the possibility to run BEAM code on really small systems like MCUs.

Intro​

According to Wikipedia X32 ABI page:

The x32 ABI is an application binary interface (ABI) and one of the interfaces of the Linux kernel. The x32 ABI provides 32-bit integers, long and pointers (ILP32) on Intel and AMD 64-bit hardware. The ABI allows programs to take advantage of the benefits of x86-64 instruction set (larger number of CPU registers, better floating-point performance, faster position-independent code, shared libraries, function parameters passed via registers, faster syscall instruction) while using 32-bit pointers and thus avoiding the overhead of 64-bit pointers.

So, I'm wondering if it would be possible to enable x32 support in Erlang/OTP build. That way, I could make a Yocto image for x32 that runs on x86-64 machines.

We've added support for the following new Erlang/OTP releases:

In additional to those new versions, a new beamtools is available here.

This new version was made with Yocto mickledore release and brings Erlang/OTP 26.0.2 and Elixir 1.15.2.

Yocto Project has released a new version 4.2 (Mickledore). As consequence meta-erlang brings a new branch mickledore updating most of the recipes. mickledore release is not a LTS release and community support will be available until November 2023.

We've also upgraded to the latest Erlang/OTP and Elixir releases supporting the following new Erlang/OTP releases:

• Erlang/OTP 26.0.1
• Erlang/OTP 25.3.2.2
• Elixir 1.14.4

It's worth mentioning the meta-erlang master has also been updated.

We've added support for the following new Erlang/OTP releases:

Removed recipes:

• For langdale the recipes ejabberd and emqx have been removed due the lack of supporting cross-compilation build in a stable way.

Updated recipes:

• For langdale the following recipes have been updated: lux, vernemq, yaws, tsung, riak, couchdb. It is important to mention about langdale EOL in May 2023. So, this branch will not receive updates.

It has been decided:

• Dropped support to Erlang/OTP 24 in langdale. Due the lack of deterministic build flags in 24. Elixir 1.12 has also been dropped (because it dependes on Erlang/OTP 24).

Intro​

The meta-erlang on cloud II, build your own application post has shown the basic idea for how would be possible (and in fact it is possible) to build a custom Linux distribution and run it on Graviton AWS instances.

Intro​

The Yocto Project has been made to create specific embedded Linux distributions. And still does a great job on this field making it possible to run softwares in a range of target architectures.

We've added support for the following new Erlang/OTP releases:

Fixed bugs:

• QA Issue buildpaths (reproducible builds) when building with langdale, a specific patch has been integrated in order to avoid building flags into the final beam.smp binary.

To be decided:

• Yocto Langdale release has enabled reproducible build checks. Erlang/OTP from 25 and later implements special flags to fix reproducible issues. But Erlang/OTP 24 does not have these special flags as a consequence langdale Erlang/OTP 24 builds warns about: packages contains reference to TMPDIR [buildpaths]. There are two paths that we could get. One is to drop Erlang/OTP 24 support OR disable QA buildpaths checking.

This new website is based on Docusaurus documentation framework. The previous site was using docsify, which is also great. But Docusaurus address others concerns when writing documentation for open source project.

So, the site has a new frontend page and a blog session where we want to add latest meta-erlang release highlights. The documentation session is pretty much the same plus some improvements on Introduction chapter.