4 include('menulist.html');
5 include('static-configuration');
11 That nice snippets of C code should be moved out of junkcode
12 directories and exposed to a wider world, where they can become
17 CCAN is loosely modelled after the successful <a href="http://cpan.org">CPAN project</a>
18 for Perl code development and sharing.
23 <p> You can get each module as a tarball (<a href="list.html">see
24 list</a>), get a tarball of <a href="ccan.tar.bz2">the whole repository</a> with tools,
25 or clone our <a href="http://git.ozlabs.org/?p=ccan">git repository</a> (<tt>git clone git://git.ozlabs.org/~ccan/ccan</tt>).
30 There are two ways to use it:
32 <li> Put modules into a ccan/ subdirectory into your project. Add a "config.h" (like
33 <a href="example-config.h">this example</a>, or generate one using <a href="http://git.ozlabs.org/?p=ccan;a=blob_plain;f=tools/configurator/configurator.c">the configurator</a>) and compile every .c file
34 in ccan/* (as in this <a href="Makefile-ccan">Makefile</a>)).
36 <li> Alternatively, just hack whatever parts you want so it compiles in
43 We always welcome new code! Copy an existing module and run the "ccanlint"
44 tool over it, or just send any code you have lying around any let someone
48 <p>Anyone can send code or a git pull request to
49 the <a href="http://ozlabs.org/mailman/listinfo/ccan">friendly
50 mailing list</a> or just <a href="upload.html">upload it using the web form</a>.
54 "GPLv2 or later" and supersets thereof (eg. LGPLv2+ or BSD)
58 <h2>Complaints, Ideas and Infrastructure</h2>
61 We have a <a href="http://ozlabs.org/mailman/listinfo/ccan">low volume
62 mailing list</a> for discussion of CCAN in general, and you're welcome
67 We also have an IRC channel: #ccan on <a href="http://freenode.net">Freenode</a>.
71 We also have a <a href="Wiki/">wiki</a>; feel free to enhance it.