very interested in this project, bearssl is released as beta quality, not sure how active it is developed these days but I'm happy to get rid of the heavy openssl when possible especially for embedded devices.
h2o still is pretty modular and it's easy to for example rip out their http/1.1 parser and use it. Other projects tend to accumulate a large utils.h or similar over time wrapping every other libc function, have typedefs, macros left and right etc. so you'd either pull all this in too or spend a few days undoing everything.
Question: what is the state of thinking behind managing external dependencies in C? This project appears to just check them into source, which is pretty simple, and I am tempted to do so on my own projects. Is this the preferred method after years of not-so-popular attempts at package managers and various issues with things like CMake external sources, github submodules/subrepos or custom scripts to download source?
One approach some recommend is single file headers, which are self contained libraries that require nothing more than an include most of the time. Search "single file headers" for more info.
Package managers (haven't tried them) and vendoring (checking into source) are the other approaches I know of.