How to help get raylib to compile to a static zig binary?

[Always-Self-Hosted]

The upstream raylib repo has adopted a zig build which is great! But unfortunately it doesn't compile into a static binary. For example on my LMDE 6 machine using the X11 backend option (no wayland) I get this:

$ ldd zig-out/bin/raylib-game
linux-vdso.so.1 (0x00007ffff1afe000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f50a445f000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f50a427e000)
/lib64/ld-linux-x86-64.so.2 (0x00007f50a455d000)

I can see in their build.zig there is quite a few other linked system libraries for other OS too.

I guess what I wanted to ask is how big of a job would it be to start forking all the upstream dependencies to this org and get them building using zig to static libraries? It's not clear to me because I don't even understand why vdso shows up as a system linked library because raylib doesn't link that? (must be one of raylibs dependencies has a dependency on vdso?)

Curious others thoughts on this and any information or breadcrumbs you can give to a enthusiastic but newer ziguana to help solve this problem

[kristoff-it]

When it comes to GUI applications on Linux, in practice you will need to do dynamic linking at some point. I don't know if this specific setup is optimal or if could be improved, but just beware of that.

[Always-Self-Hosted]

@kristoff-it I wasn't aware of that so thank you very much for the information! I guess that definitely makes this endeavour far less appealing as I envisioned getting to a point where everything compiles down to a static binary that I can just ship for a given target.

I guess you've given me a rabbit hole to go down now given I clearly don't understand graphics well enough.