4 ms·
> As has been mentioned in other comments already, Linux has a stable ABI so you don't need a libc at all. Unless you want to use graphics acceleration, which
by account42 5y ago
> As has been mentioned in other comments already, Linux has a stable ABI so you don't need a libc at all.
Unless you want to use graphics acceleration, which is implemented in userspace as harware-specific dynamic libraries. Audio also typically goes through user-space implementations - not sure if the interprocess protocols there are stable enough to statically the client libraries.
- dundarious 5y agoDefinitely, was just describing the base level reality that you can in theory just use syscalls and skip libc. In practice, that doesn't mean there are "enough" useful kernel interfaces or graphics libraries implemented right now that also skip libc. Much like how there might not be enough no_std compatible crates available in rust. For systems programming, I find nolibc and kernel32 adequate.