Small announcement: I intend to continue the development of the meson language server: https://github.com/JCWasmx86/mesonlsp

The repo is unarchived again, so feel free to open issues, bugs, features request.

As first measure I will clean up the 1.5 years of missed meson developments.

#meson #mesonbuild

Over the last months the Rust/cargo support in meson improved a lot.

It's now ready to build and install a GTK4 Rust application with around 70 dependencies without having to write almost any custom build glue for the dependencies.

https://github.com/sdroege/mandelbrot#meson-build

The application in question is just a small experiment of mine for rayon and GTK4 input handling / rendering. The more or less same should work for other GTK4 applications at this point.

All this still depends on two unmerged meson PRs, but it's a huge step forward from the situation just a few months ago.

Thanks to the hard work of @xclaesse and dcbaker!

I hope in the future this will allow GNOME applications written in Rust to have a less strange and fragile build setup than what they have right now with mixing cargo and meson.

#rustlang #rust #gtk #gnome #meson #mesonbuild

I wrote a thing about how I've been using the #ZigLang toolchain to cross-compile small tools (almost) effortlessly. Not that I used the programming language itself much, but the “zig cc” tooling is great! The article also features #MesonBuild, which I like to call “the least annoying of build systems, probably”.

You can read it here: https://perezdecastro.org/2023/standalone-binaries-zigcc-meson.html

I’ve been looking at Meson for a little while, and I generally like it. But there doesn’t seem to be any way to extend it or write macro-like constructs. For example, if I want to build something with lots of plugins, I can’t wrap the build definition of a plugin and then apply that every where. I think that makes it a bit impractical for many builds.

#meson #mesonbuild