| 1 |
== link:index.html[Index] -> link:basics.html[Getting started] -> link:basics_installation.html[Installation] |
|---|
| 2 |
|
|---|
| 3 |
Installatoin from SVN |
|---|
| 4 |
--------------------- |
|---|
| 5 |
|
|---|
| 6 |
The latest, bleeding edge Cherokee release can always be retrieved via |
|---|
| 7 |
SVN. Note that this is the development release and could very well be |
|---|
| 8 |
unstable. In general it is not recommended to run this release in |
|---|
| 9 |
production environments. |
|---|
| 10 |
|
|---|
| 11 |
Briefly, SVN is a system tool used to store and maintain files and a |
|---|
| 12 |
history of their changes over time, and it is an ivaluable development |
|---|
| 13 |
tool. The Cherokee source code and related files are kept on a SVN |
|---|
| 14 |
server at svn.cherokee-project.com. |
|---|
| 15 |
|
|---|
| 16 |
To download the SVN repository you will need a special piece of |
|---|
| 17 |
software called an SVN client. |
|---|
| 18 |
|
|---|
| 19 |
[[checkout]] |
|---|
| 20 |
Checking out the sources |
|---|
| 21 |
~~~~~~~~~~~~~~~~~~~~~~~~ |
|---|
| 22 |
To list the available modules, type: |
|---|
| 23 |
|
|---|
| 24 |
---- |
|---|
| 25 |
svn list svn://svn.cherokee-project.com/ |
|---|
| 26 |
---- |
|---|
| 27 |
|
|---|
| 28 |
To check out the sources for the first time from the repository, use this command: |
|---|
| 29 |
|
|---|
| 30 |
---- |
|---|
| 31 |
svn co svn://svn.cherokee-project.com/cherokee/trunk cherokee |
|---|
| 32 |
---- |
|---|
| 33 |
|
|---|
| 34 |
[[update]] |
|---|
| 35 |
Updating the sources |
|---|
| 36 |
~~~~~~~~~~~~~~~~~~~~ |
|---|
| 37 |
|
|---|
| 38 |
To update your sources every day, you use this command: |
|---|
| 39 |
|
|---|
| 40 |
---- |
|---|
| 41 |
svn up cherokee |
|---|
| 42 |
---- |
|---|
| 43 |
|
|---|
| 44 |
|
|---|
| 45 |
[[compile]] |
|---|
| 46 |
Compiling and installing |
|---|
| 47 |
~~~~~~~~~~~~~~~~~~~~~~~~ |
|---|
| 48 |
|
|---|
| 49 |
Once you have downloaded the latest SVN revision, you will need to |
|---|
| 50 |
follow the installation instructions for your specific platform. |
|---|
| 51 |
|
|---|
| 52 |
Note that some of the files present in the tarball are not present in |
|---|
| 53 |
SVN. Most noticeably, the file `./configure` that will be needed for the |
|---|
| 54 |
installation process. |
|---|
| 55 |
|
|---|
| 56 |
To generate the missing files simply run this command: |
|---|
| 57 |
|
|---|
| 58 |
---- |
|---|
| 59 |
./autogen.sh |
|---|
| 60 |
---- |
|---|
| 61 |
|
|---|
| 62 |
As optional parameters, you can specify any option you want relayed |
|---|
| 63 |
to `./configure`. This way you can avoid issuing another command for |
|---|
| 64 |
the configuration. |
|---|
| 65 |
|
|---|
| 66 |
For instance, this line will configure your local copy with the four |
|---|
| 67 |
specified parameters: |
|---|
| 68 |
|
|---|
| 69 |
---- |
|---|
| 70 |
./autogen.sh --prefix=/usr --sysconfdir=/etc \ |
|---|
| 71 |
--localstatedir=/var --enable-trace |
|---|
| 72 |
---- |
|---|
| 73 |
|
|---|
| 74 |
You would then be ready to proceed with the standard compilation |
|---|
| 75 |
process for your platform: |
|---|
| 76 |
|
|---|
| 77 |
* link:basics_installation_unix.html[Unix installation] |
|---|
| 78 |
* link:basics_installation_windows.html[Windows installation] |
|---|