release of the display server , which is still being developed by Canonical, despite the discontinuation of the Unity shell and the Ubuntu edition for smartphones. Mir remains in demand for Canonical's projects and is now positioned as a solution for embedded devices and the Internet of Things (IoT). Mir can be used as a compositing server for Wayland, allowing any applications that utilize Wayland (for example, those built with GTK3/4, Qt5, or SDL2) to run in Mir-based environments. Installation packages are prepared for Ubuntu 18.04-20.10 () and . The project's code is licensed under GPLv2.
The significant version number change is due to breaking changes in the API that compromise compatibility and the removal of some deprecated APIs. Specifically, support for the specific APIs mirclient and mirserver has been discontinued, with the Wayland protocol now recommended for use instead. The libraries associated with mirclient and mirserver remain, but they are now only used for internal purposes, do not provide header files, and do not guarantee ABI stability (a major code cleanup is planned for the future). The discontinuation of the specified APIs has been agreed upon with the UBports project, which continues to use mirclient in Ubuntu Touch. It has been decided that the capabilities of Mir 1.x are sufficient for the needs of UBports at this time, and in the future, the project can transition to Mir 2.0.
The removal of mirclient also allowed for the elimination of support for certain interfaces for graphic platforms that were only used in the mirclient API. It is noted that this simplification will not lead to visible changes and will serve as a basis for improving the code for platform support, especially in the area of multi-GPU systems, headless operation, and the development of remote desktop access tools.
As part of the ongoing cleanup, specific mesa dependencies have been removed from the mesa-kms and mesa-x11 platforms — only gbm is retained as a dependency, which has enabled Mir to function atop X11 on systems with NVIDIA drivers. The mesa-kms platform has been renamed to gbm-kms, and mesa-x11 to gbm-x11. A new rpi-dispmanx platform has also been added, allowing the use of Mir on Raspberry Pi 3 boards with Broadcom drivers. In the MirAL (Mir Abstraction Layer) layer, which can be used to avoid direct interaction with the Mir server and abstract ABI access through the libmiral library, the option to enable and disable window decoration on the server side (SSD) has been added, along with the ability to configure scaling within the DisplayConfiguration block.
Source: opennet.ru
