At some point the code is more or less Done(tm), and you spend the rest of your life fucking with the build system, as people's opinions change on how it should work.
@Di4na@msw Centricular recently paid for librsvg to be ported from Autotools to Meson; they did a fantastic job. But the build scripts are not easy, even in Meson! It needs to do Special Stuff(tm) to call cargo and have everything work on Windows and MacOS.
It's mostly stupid glue. Cargo puts artifacts in one place; meson wants them in another. Meson knows the file extensions for libraries or binaries depending on the platform, but does not expose them, so the build scripts replicate them.
@Di4na@msw There's an uncomfortable amount of Python to build symbol lists on Windows. Meson needs a duplicated list of source files, even if cargo detects them automatically. Meson's concept of the build configuration needs to be translated to cargo's concept, and the cargo-wrapper script has subtle differences when called for "build" vs. "test".
On Windows, when FreeType builds don't provide pkg-config, they fall back to cmake. And librsvg's meson foo needs to adapt to that.
Add comment