3 ms·
[http://blog.ashworth.in/2014/10/19/the-advent-of-clib-the-c-package-manager.html http://blog.ashworth.in/2014/10/19/the-advent-of-clib-the-c-...]: > "Finally:
by eqvinox 6y ago
[http://blog.ashworth.in/2014/10/19/the-advent-of-clib-the-c-package-manager.html http://blog.ashworth.in/2014/10/19/the-advent-of-clib-the-c-...]:
> "Finally: a place where C programmers can get together and collaborate on open source, then distribute their code - in a centralized, easy way."
That place already exists. In fact, at least two such places exist: GLib and APR.
Also, this is not how C development workflow works.
- ausjke 6y agoneither of them are widely used, glib is pretty large(1MB at least, OK for desktop but too large for embedded, for example) and apr's function is limited. clib can let you integrate small pkgs at will at source level, sometimes it is very handy and useful.
- SQueeeeeL 6y agoAm I just too dumb to understand this; because I thought this was what linkers and header files were for
- closeparen 6y agoLanguage package managers take care of versioning/downloading the library from a central source into a project-specific place where the toolchain will find it. AFAIK for C, this is handled by your linux distribution, and for any libraries that are not part of your distro you would be downloading the header and object files / pointing your Makefile at them by hand.