Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is also (IMO) what bionic is great for. It's also licensed compatibly, whereas the rest aren't.


I don't think Bionic is really suitable for this. It's unlikely to even work for building apps that weren't specifically designed for Bionic, since it's rather deficient in its support for many of the standard functions, and also differs moderately from glibc and other more popular libcs in the extensions it provides. Really Bionic was just created to be the minimal libc needed to run Dalvik (Google's "JVM") and everything else looks like an afterthought. I'd really like to add Bionic to the comparison table, but I haven't found a way to build it outside of building a whole Android development environment, which is a huge headache...


Bionic is very incomplete though. it is not really worth using outside Android you may as well use Musl.


Musl (looks like) doesn't support aarch64 and aarch32, so if you're targeting those it's not even an option.


Could you clarify what you mean by "doesn't support aarch32"? I can't find any clear definition of what aarch32 means, but my impression is that it's just a new name for what we call "arm", but possibly implying new instructions available on v8, and the ABI is the regular 32-bit ARM EABI. If so musl supports it just fine.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: