I’ve been working on a C utility library called everyutil-c over the past few months, and wanted to finally share it here. It's a lightweight but powerful collection of utility functions, designed with performance, clarity, and portability in mind.
A few things we focused on:
Clean, well-documented API
Modular components (pull in only what you need)
Full test coverage
Easy builds: works out of the box with Make, Autotools, or CMake
Cross-platform: Linux, macOS, and Windows (with proper DLL export handling)
New build.sh script for smoother setup, especially in environments like MSYS2
We recently rewrote the array utilities for better performance and maintainability, which felt like a good milestone to share this more broadly.
If you use C regularly (or even just occasionally), I’d really love to hear your feedback. What do you value most in a utility lib? Have you run into issues when integrating small C libraries into larger projects—especially when dealing with multiple platforms or compilers?
Also curious: if you’ve used other libraries like stb, klib, or GLib, what worked for you and what didn’t?
Feedback, ideas, bug reports, feature requests—all are welcome. Repo link is in the comments if you want to check it out or contribute.
The lack of API doc's for the c version is kind of frustrating. It makes it impossible for someone to evaluate whether or not your library is suitable for something they need. Or if it is, how to use properly.
everyutil-c is a modern, modular C utility library crafted to provide a wide collection of robust, reusable functions that simplify everyday low-level programming tasks across platforms. It acts as a “standard library extension,” bundling together well-tested logic for common needs such as array manipulation, string processing, number utilities, and more all with performance and portability in mind. The API is intentionally designed to be clean and intuitive, exposing clearly documented headers and consistent function signatures, making it easy to drop into existing projects. Under the hood, the implementation emphasizes speed and reliability, with careful memory handling and minimal external dependencies. The library is thoroughly tested using a dedicated test suite to ensure correctness and stability across use cases. everyutil-c supports multiple build systems Makefiles, Autotools, and CMake and provides an automated build.sh script that can even fetch dependencies and configure environments like MSYS2 on Windows. Recent enhancements include a major refactor of array utilities (e.g., more efficient iteration, memory-safe operations), improved build scripts, and better platform abstraction.
*everyutil-js is JavaScript version of it (identically clone)
I’ve been working on a C utility library called everyutil-c over the past few months, and wanted to finally share it here. It's a lightweight but powerful collection of utility functions, designed with performance, clarity, and portability in mind.
A few things we focused on:
Clean, well-documented API
Modular components (pull in only what you need)
Full test coverage
Easy builds: works out of the box with Make, Autotools, or CMake
Cross-platform: Linux, macOS, and Windows (with proper DLL export handling)
New build.sh script for smoother setup, especially in environments like MSYS2
We recently rewrote the array utilities for better performance and maintainability, which felt like a good milestone to share this more broadly.
If you use C regularly (or even just occasionally), I’d really love to hear your feedback. What do you value most in a utility lib? Have you run into issues when integrating small C libraries into larger projects—especially when dealing with multiple platforms or compilers?
Also curious: if you’ve used other libraries like stb, klib, or GLib, what worked for you and what didn’t?
Feedback, ideas, bug reports, feature requests—all are welcome. Repo link is in the comments if you want to check it out or contribute.
Thanks!
https://github.com/dailker/everyutil-js
https://github.com/dailker/everyutil-c
The lack of API doc's for the c version is kind of frustrating. It makes it impossible for someone to evaluate whether or not your library is suitable for something they need. Or if it is, how to use properly.
README.MD to navigate on GitHub via markdown links
oh i got you i will add that to C version. I was kinda lazy after JS. Definitely loved that idea! Thanks
We really need a description of what the library provides!
everyutil-c is a modern, modular C utility library crafted to provide a wide collection of robust, reusable functions that simplify everyday low-level programming tasks across platforms. It acts as a “standard library extension,” bundling together well-tested logic for common needs such as array manipulation, string processing, number utilities, and more all with performance and portability in mind. The API is intentionally designed to be clean and intuitive, exposing clearly documented headers and consistent function signatures, making it easy to drop into existing projects. Under the hood, the implementation emphasizes speed and reliability, with careful memory handling and minimal external dependencies. The library is thoroughly tested using a dedicated test suite to ensure correctness and stability across use cases. everyutil-c supports multiple build systems Makefiles, Autotools, and CMake and provides an automated build.sh script that can even fetch dependencies and configure environments like MSYS2 on Windows. Recent enhancements include a major refactor of array utilities (e.g., more efficient iteration, memory-safe operations), improved build scripts, and better platform abstraction.
*everyutil-js is JavaScript version of it (identically clone)