single_file_libs VS clib

Yep: https://github.com/nothings/single_file_libs

Also sometimes I use only header (.h) with all functions included wrapped by #ifndef and #endif. When I use these? for code that I always reuse to simplify things and some data stucture handling (to implement dynamic arrays). A good example list of these (not mine) are https://github.com/nothings/single_file_libs

Also, there are many libraries that are much bigger (little list I found) but are implemented in a single header file.

If others have a similiar problem, I found a great github page that has lots of single header libraries, including data structures.

> Like, why don't we just let projects be "done"? Things don't need to be maintained and updated for eternity.

This is generally why I opt for "single-file" libraries that do one simple task well. The smaller the library, the more likely it is "done". For example, do I want some insanely complex image library that handles every file format under the sun, or do I just want some basic one that allows me to output a simple JPEG?

I often find myself referring to "single_file_libs" repository: https://github.com/nothings/single_file_libs

Looking at the open issues, it doesn't appear to be actively maintained but it's still an incredibly good resource for "completed" projects.

Steamworks is the easy option, but if you're programming-savvy you could also use a networking library (some lists for C and C++: 1 2 3) to accomplish the same thing.

Have a look at these. https://github.com/nothings/single_file_libs#geometry-file

For smaller c libraries, there's https://github.com/clibs/clib, but I don't know how often it's updated.

C Package Manager\ (59 comments)

Projects: apex/up, git-extras, koajs/koa, clibs/clib, commander.js