2 ms·
Base system libraries like glibc, OpenGL, Vulkan, libasound, etc. all provide a stable userland ABI. What doesn't work is relying on random other libraries to
by account42 5y ago
Base system libraries like glibc, OpenGL, Vulkan, libasound, etc. all provide a stable userland ABI.
What doesn't work is relying on random other libraries to be present, but you will run into the same problem if you rely on whatever some other program dumped into system32 on windows. You also can't link against a newer glibc/etc. and then expect to run on older versions - that is not inherently different on Windows either but the SDK does let you target older versions from modern toolchains (whith limitations), something that GNU unfortunately does not care to provide so you have to make your own (or search for one).
- yc12340 5y agoGlibc, libasound and other key libraries have poor compatibility history, which can be seen from their sonames: libc.so.6 libasound.so.2 libfreetype.so.6 libX11.so.6 Each glibc/ALSA soname bump can spell death to entire generation of binary software. In theory, you can link libX11, openssl and other important libraries statically, but many developers don't do it, because of weird concerns about "security", "compatibility" etc. Compare it to Windows, where libraries like kernel32, user32 and gdi32 remained stable for decades and statically linking to them is unnecessary by design.