Package manager for the C programming language.
$ npm install -g clib
Basically the lazy-man's copy/paste promoting smaller C utilities, also
serving as a nice way to discover these sort of libraries. From my experience
C libraries are scattered all over the web and discovery is relatively poor. The footprint of these libraries is usually quite large and unfocused. The goal of clibs is to provide
stand-alone "micro" C libraries for developers to quickly install without coupling
to large frameworks.
The wiki listing of packages acts as the "registry" and populates the cpm-search(1) results.
You should use clib(1) to fetch these files for you and check them into your repository, the end-user and contributors should not require having clib(1) installed.
Usage: clib [options] [command]
Commands:
install <pkg> install the given package(s)
search [query] search available packages
help [cmd] display help for [cmd]
Options:
-h, --help output usage information
-V, --version output the version number
Install a few dependencies to ./deps:
$ clib install visionmedia/ms.c visionmedia/commander.c
Install them to ./src instead:
$ clib install visionmedia/ms.c visionmedia/commander.c -o src
Install some executables:
$ clib install visionmedia/mon visionmedia/every visionmedia/watch
Once again with brace expansion, you do love brace expansion right? ;)
$ clib install visionmedia/{mon,every,watch}
Example of a package.json explicitly listing the source:
{
"name": "term",
"version": "0.0.1",
"repo": "clibs/term",
"description": "Terminal ansi escape goodies",
"keywords": ["terminal", "term", "tty", "ansi", "escape", "colors", "console"],
"license": "MIT",
"src": ["src/term.c", "src/term.h"]
}Example of a package.json for an executable:
{
"name": "mon",
"version": "1.1.1",
"repo": "visionmedia/mon",
"description": "Simple process monitoring",
"keywords": ["process", "monitoring", "monitor", "availability"],
"license": "MIT",
"install": "make install"
}MIT