| | 1 | [wiki:neercs << back to neercs] |
| | 2 | |
| | 3 | = neercs development notes = |
| | 4 | |
| | 5 | This page explains how to build and hack on neercs. |
| | 6 | |
| | 7 | == Getting the source code == |
| | 8 | |
| | 9 | The source code is managed in a Subversion repository. You can [/browser/neercs/trunk browse it online] for a quick overview of what is happening. |
| | 10 | |
| | 11 | Use the following command to retrieve the source code: |
| | 12 | |
| | 13 | {{{ |
| | 14 | svn co svn://svn.zoy.org/caca/neercs/trunk neercs |
| | 15 | }}} |
| | 16 | |
| | 17 | == Building using the autotools == |
| | 18 | |
| | 19 | Using the autotools solution is the preferred way to build neercs. It is complicated but you can trust us to maintain it properly. Building neercs is then a 3-step operation: bootstrapping, configuring and building. |
| | 20 | |
| | 21 | {{{ |
| | 22 | ./bootstrap |
| | 23 | ./configure |
| | 24 | make |
| | 25 | }}} |
| | 26 | |
| | 27 | This will build [wiki:neercs]. |
| | 28 | |
| | 29 | == Design == |
| | 30 | |
| | 31 | An overview of the neercs architecture: |
| | 32 | |
| | 33 | [[Image(design.png)]] |
