So Github user @chadchoi was right. They said it's not thread models mismatch but libstdc++ versions mismatch.

I was apparently wrong in this case, sorry.

librsvg is written in Rust. This is what happens when you introduce Rust into a C project. The binary generated by Rust tends to boom in size. This is normal. I don't think librsvg was linked statically into the loader as you have guessed.

That's clear (I already had my share of issues with this particular library and the macOS port). But there are 2 libraries - the actual librsvg library and the loader which is just a very thin library. I haven't checked in what language the loader is written but on my Debian linux it looks this way - pretty much like all the rest:

-rw-r--r-- 1 root root 67640 Jun 13  2024 libpixbufloader-ani.so
-rw-r--r-- 1 root root 67656 Jun 13  2024 libpixbufloader-bmp.so
-rw-r--r-- 1 root root 67640 Jun 13  2024 libpixbufloader-gif.so
-rw-r--r-- 1 root root 67640 Jun 13  2024 libpixbufloader-icns.so
-rw-r--r-- 1 root root 67712 Jun 13  2024 libpixbufloader-ico.so
-rw-r--r-- 1 root root 67696 Jun 13  2024 libpixbufloader-pnm.so
-rw-r--r-- 1 root root 67664 Jun 13  2024 libpixbufloader-qtif.so
-rw-r--r-- 1 root root 67376 Jul 30  2023 libpixbufloader-svg.so
-rw-r--r-- 1 root root 67648 Jun 13  2024 libpixbufloader-tga.so
-rw-r--r-- 1 root root 67648 Jun 13  2024 libpixbufloader-tiff.so
-rw-r--r-- 1 root root 67536 Mar  4  2023 libpixbufloader-webp.so
-rw-r--r-- 1 root root 67640 Jun 13  2024 libpixbufloader-xbm.so
-rw-r--r-- 1 root root 67640 Jun 13  2024 libpixbufloader-xpm.so

But of course it's hard to compare, maybe on Windows there's some extra boilerplate code that has to be added.

After checking msys2/MINGW-packages@a2aaa55#diff-0db33fcf01a542992efe526a1612edefac816309632a06fc2b7348ce2ae5b66c and subsequent commits in more detail, they switch from autotools to meson and there may be so many things that meson does differently that there's probably no easy way to figure out, what it is.

So while hacky, updating the cache manually will probably be the only option for now.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <geany/geany/pull/4088/c2560932407@github.com>