Hey HN! Over the past few months, I’ve been building a C utility library called everyutil-c, aimed at providing a robust, high-performance set of logic and utility functions with an emphasis on clean design and cross-platform support. It includes a well-documented API, a comprehensive test suite, and flexible build options—Makefile, Autotools, and CMake are all supported out of the box. We also made sure to handle Windows builds via DLL export, alongside full support for Linux and macOS.
We recently hit a milestone with a refactor of our array utilities for better performance and maintainability, and rolled out a build.sh script to make getting started a lot smoother—especially for folks working in MSYS2 or on platforms where toolchains can get messy. The library is fully modular, with functions separated into reusable components, and we’ve put a lot of effort into keeping things simple without sacrificing flexibility or efficiency.
If you're a C developer (or even dabble in C occasionally), I’d love to get your thoughts. What do you usually look for in a utility library? Are there any pain points you run into when trying to integrate small helper libraries into bigger projects—especially across platforms? Also curious if you’ve had good or bad experiences with other utility libs like GLib, klib, or stb, and what we could learn from those. All feedback is welcome, and if you're up for it, PRs and issues are open too. Repo link in the comments!
2
1