ERROR: Unsupported linker, only bfd, gold, and lld are supported, not ld.bfd.
Fucking buildsystems (meson this time), none of them are good.
- Be as agnostic as possible: Don't hardcode, use pkg-config or environment variables on pretty much everything
- Don't test if the OS works, that's not our problem
- Strongly avoid workarounds, OS should be fixed instead or more portable methods should be used
checking for glGetString in -lGL... no configure: error: Unable to locate required GL library
How many fucking things will I have to fix in the very same way…
> Clutter still depends on it
What the fuck are you doing GNOME.
> Clutter is in deep maintenance mode; only micro releases addressing bug fixes
are planned from now on. Additionally, the API and features are frozen.
> The planned replacement for Clutter is GTK 4.0.
> https://gitlab.gnome.org/GNOME/clutter/-/merge_requests/5
> been broken in wlroots for several years
Which has a page about La+, so Yeet My Dark.
https://cogl3d.org/ymd/
@lanodan @kirby
meson is as good as autotools, except it's python instead of m4. With both I can see why things break and fix it, would that be idiomatic? Not so sure. I don't get why people hate autotools — sure, it's lots of generated boilerplate code, but you can figure out what ti does just by looking at it. Unlike CMake — which is pure evil!
@lanodan @kirby
You won' understand what it does, no matter how long you look at it — without reading the docs. I don't know why it got so popular TBH — it's probably good at handling most common cases on most common platform and it *makes it look* like there is no or little boilerplate code. And I've never seen artifacts included with releases — you still have to have CMake itself installed, it has to be of more or less recent version.
Like here's a meson implementation without python: https://muon.build/
And it's non-reviewable, even the autotools-m4 files are arcane enough that I'd say it's a delusion if you think you can review this stuff without wasting hours each time. Worst part is how it's not something like libraries where it's somewhat isolated, it's collections of templates.
@lanodan @kirby
Yes, that is so! It's only "fixable" in a sense that you can make some software get built right here right now, finding fundamental flaws and submitting the fix upstream would sure take a lot of effort, but with CMke even that is impossible, because I just don't understand how it works under the hood, it's just a black box.
Well it's more like, good ones:
- straightforward Makefile
- simple configure script (as seen in musl, vis, some portable BSD software, …) + static Makefile
Meanwhile:
- meson: Occasionally a pain but usually fixable, good enough for me to recommend it
- CMake: Impossible to debug, out
- autotools: Not only the artifacts are a proven vector for malware, even the actual sources are a PITA to read (Imagine adding more complexity to raw m4)
- scons, waf, …: Basically autotools but in other languages
- premake: vendored curl+mbedtls? Without proper security updates? Nope. (see https://bugs.gentoo.org/773475)