Changeset 210 for trunk/docs/kernel
- Timestamp:
- May 6, 2011, 6:55:54 PM (14 years ago)
- File:
-
- 1 edited
-
trunk/docs/kernel/installation.txt (modified) (14 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/docs/kernel/installation.txt
r136 r210 8 8 :backlinks: top 9 9 10 This page provides documentation on how to compile then install ZOO-Kernel on Unix and Win32 platforms. 10 This page provides documentation on how to compile then install the ZOO Kernel on Unix and Win32 platforms. 11 12 Obtaining the ZOO Kernel Source 13 ------------------------------- 14 15 Use the following command to get the ZOO Kernel source code through Subversion: 16 17 :: 18 19 svn checkout http://svn.zoo-project.org/svn/trunk zoo-project 20 21 For users which get a developer account, use the following: 22 23 :: 24 25 sed "s:\[tunnels\]:\[tunnels\]\nzoosvn = /usr/bin/ssh -p 1046:g" -i ~/.subversion/config 26 svn co svn+zoosvn://svn.zoo-project.org/var/svn/repos/trunk zoo-project 27 28 The first line of the instruction above defines a specific tunnel to access the svn server through 29 the SSH protocol. Indeed, the ZOO SVN server listens on the 1046 (1024+22) port rather than the default one (22). 30 31 Prerequisites 32 ------------- 33 34 The following libraries are required on your system before you can install the ZOO Kernel: 35 36 - autoconf ( http://www.gnu.org/software/autoconf/ ) 37 - cgic ( http://www.boutell.com/cgic ) 38 - cURL ( http://curl.haxx.se ) 39 - FastCGI ( http://www.fastcgi.com ) 40 - Flex & Bison ( http://flex.sourceforge.net/ http://www.gnu.org/software/bison/ ) 41 - libxml2 ( http://xmlsoft.org ) 42 - OpenSSL ( http://www.openssl.org ) 43 - Python ( http://www.python.org ) 44 45 Optional libraries include: 46 47 - PHP Embedded (optional) ( http://www.php.net ) 48 - Java SDK (optional) ( http://java.sun.com ) 49 - SpiderMonkey (optional) ( http://www.mozilla.org/js/spidermonkey/ ) 50 51 Compile libcgic 52 --------------- 53 54 The first step is to compile libcgic from the ``zoo-project/thirds`` directory. For such a task, please use 55 the following command: 56 57 :: 58 59 cd thirds/cgic206 60 make 61 62 Make sure that a ``libcgic.a`` is created in your ``zoo-project/thirds/cgic206`` directory. If yes, then 63 you can go to the next step. 64 65 On Windows, rather than using the make command, please use: 66 67 :: 68 69 nmake /f makefile.vc. 70 71 .. warning:: 72 If you don't compile libcgic first, and try to compile the ZOO Kernel, you will get an error such as *cannot find -lcgic* 11 73 12 74 Unix 13 75 ---- 14 76 15 For Unix users, ZOO-Kernel comes with a GNU autoconf "configure" script that should take care of (hopefully!)77 For Unix users, the ZOO Kernel comes with a GNU autoconf "configure" script that should take care of (hopefully!) 16 78 all compilation issues for you. 17 79 18 The configure script won't work on Windows. See section WIN32 for details on compiling on Windows systems. 80 The configure script won't work on Windows. See section :ref:`WIN32 <win32>` for details on compiling 81 on Windows systems. 19 82 20 83 For the impatient 21 84 ***************** 22 85 23 To build zoo_loader.cgi CGI program with the default options, go to the default options, goto the directory24 where you extracted the ZOO -Kernel source code package and use the following command:86 To build the ``zoo_loader.cgi`` CGI program with the default options, cd to the directory 87 where you extracted the ZOO Kernel source code package and use the following commands: 25 88 26 89 :: 27 90 28 91 $ cd zoo-kernel 92 $ autoconf 29 93 $ ./configure 30 94 $ make 31 95 32 Unless something went wrong, you should have executables in the current directory for the zoo_loader.cgi33 CGI program. You can copy the zoo_loader.cgi program and the main.cfgfile to your HTTP server's CGI96 Unless something went wrong, you should have executables in the current directory for the ``zoo_loader.cgi`` 97 CGI program. You can copy the ``zoo_loader.cgi`` program and the ``main.cfg`` file to your HTTP server's CGI 34 98 directory and start using it. 35 99 36 100 At this step your ZOO-Kernel should work. Nevertheless, don't forget to correct the main.cfg settings 37 to set tmpPath and tmpUrlto fit your web server configuration.101 to set ``tmpPath`` and ``tmpUrl`` to fit your web server configuration. 38 102 39 103 Configure Options … … 46 110 --with-gdal-config=FILE specify an alternative gdal-config file 47 111 --with-xml2config=FILE specify an alternative xml2-config file 48 --with-python=PATH To enable dpython support or specify an alternative112 --with-python=PATH To enable python support or specify an alternative 49 113 directory for python installation, disabled by 50 114 default 51 --with-php=PATH To enable dphp support or specify an alternative115 --with-php=PATH To enable php support or specify an alternative 52 116 directory for php installation, disabled by default 53 --with-perl=PATH To enable dperl support or specify an alternative117 --with-perl=PATH To enable perl support or specify an alternative 54 118 directory for perl installation, disabled by default 55 --with-java=PATH To enable djava support, specify a JDK_HOME,119 --with-java=PATH To enable java support, specify a JDK_HOME, 56 120 disabled by default 57 --with-js=PATH specify --with-js=path-to-js to enable djs support,121 --with-js=PATH specify --with-js=path-to-js to enable js support, 58 122 specify --with-js on linux debian like, js support 59 123 is disabled by default … … 65 129 66 130 If your gdal-config program is not found in your PATH then you can use the 67 "*--with-gdal-config*" option to speficy its location. For instance, letsuppose that your gdal-config131 ``--with-gdal-config`` option to specify its location. For instance, let's suppose that your gdal-config 68 132 was installed in /usr/local/bin and this directory is not in your PATH, then you can use 69 133 the following command: … … 77 141 78 142 If your xml2-config program is not found in your PATH then you can use the 79 "*--with-xml2config*" option to specify its location. For instance, letsuppose that80 your xml2-config was installed in /usr/local/bin end this directory is not in youPATH,143 ``--with-xml2config`` option to specify its location. For instance, let's suppose that 144 your xml2-config was installed in /usr/local/bin and this directory is not in your PATH, 81 145 then you can use the following command: 82 146 … … 88 152 ^^^^^^^^^^^^^^^^^^^^^^^^^ 89 153 90 If you want to activate the Python Support for ZOO-Kernel then you will have to use the91 "*--with-python*"option. If your python-config program is found in your PATH then you92 don't have to specify the path where Python was installed, s o using the following command:154 If you want to activate Python support for the ZOO Kernel then you will have to use the 155 ``--with-python`` option. If your python-config program is found in your PATH then you 156 don't have to specify the path where Python was installed, such as: 93 157 94 158 :: … … 96 160 $ ./configure --with-python 97 161 98 This supposethat python-config is found in your PATH.99 100 In case your python-config is not found in your PATH, then you can set the Python installation101 directory you are using. For instance, let suppose that you installed Python in /usr/local,102 then you can use the following command:162 This assumes that python-config is found in your PATH. 163 164 In the case that your python-config is not found in your PATH, then you can specify the Python 165 installation directory you are using. For instance, let's suppose that you installed 166 Python in /usr/local, then you can use the following command: 103 167 104 168 :: … … 106 170 $ ./configure --with-python=/usr/local 107 171 108 This supposethat /usr/local/bin/python-config exists.172 This assumes that /usr/local/bin/python-config exists. 109 173 110 174 (Optional) PHP Support 111 175 ^^^^^^^^^^^^^^^^^^^^^^ 112 176 113 To be able to activate PHP Support for ZOO-Kernel you'll need to get a local PHP Embedded114 installation , for more informations about configure options to use to get such kind of PHP115 installation youcan refer to this page :177 To be able to activate PHP support for the ZOO Kernel you'll need to get a local PHP Embedded 178 installation; for more information about the required configure options when compiling PHP you 179 can refer to this page : 116 180 117 181 http://zoo-project.org/trac/wiki/ZooKernel/Embed/PHP 118 182 119 If you want to activate the PHP Support for ZOO-Kernel then you will have to use the120 "*--with-php*"option. If your php-config program is found in your PATH then you don't have121 to specify the path where PHP was installed, so usingthe following commnd:183 If you want to activate the PHP support for the ZOO Kernel then you will have to use the 184 ``--with-php`` option. If your php-config program is found in your PATH then you don't have 185 to specify the path where PHP was installed, then you can use the following commnd: 122 186 123 187 :: … … 125 189 $ ./configure --with-php 126 190 127 This supposethat php-config is found in your PATH.128 129 In case your php-config is not found in your PATH, then you can setthe PHP installation130 directory you are using. For instance, let suppose that you installed PHP in /usr/local,191 This assumes that php-config is found in your PATH. 192 193 In the case that your php-config is not found in your PATH, then you can specify the PHP installation 194 directory you are using. For instance, let's suppose that you installed PHP in /usr/local, 131 195 then you can use the following command: 132 196 … … 135 199 $ ./configure --with-php=/usr/local 136 200 137 This supposethat /usr/local/bin/php-config exists.201 This assumes that /usr/local/bin/php-config exists. 138 202 139 203 (Optional) Perl Support 140 204 ^^^^^^^^^^^^^^^^^^^^^^^ 141 205 142 If you want to activate the Perl Support for ZOO-Kernel then you will have to use the143 "*--with-perl*" option. If you do not set any value to this option, thenperl program will144 be searched in your PATH. So in such case, you can use the following command:206 If you want to activate Perl support for the ZOO Kernel then you will have to use the 207 ``--with-perl`` option. If you do not set any value to this option, then the perl program will 208 be searched in your PATH. So in such a case, you can use the following command: 145 209 146 210 :: … … 148 212 $ ./configure --with-perl 149 213 150 This supposethat perl is found in your PATH.151 152 In other case, for custom Perl installation, you can set the installation directory. For instance,153 let suppose that you installed Perl in /usr/local and /usr/local/bin is not in your PATH,214 This assumes that perl is found in your PATH. 215 216 In the other case, for custom Perl installations, you can set the installation directory. For instance, 217 let's suppose that you installed Perl in /usr/local and /usr/local/bin is not in your PATH, 154 218 then you can use the following command: 155 219 … … 158 222 $ ./configure --with-perl=/usr/local 159 223 160 This supposethat /usr/local/bin/perl exists.224 This assumes that /usr/local/bin/perl exists. 161 225 162 226 (Optional) Java Support 163 227 ^^^^^^^^^^^^^^^^^^^^^^^ 164 228 165 If you want to activate the Java Support for ZOO-Kernel then you will have to use the166 "*--with-java*"option and set the installation path of your Java SDK. For instance,167 let suppose that your Java SDK was installed in/usr/lib/jvm/java-6-sun-1.6.0.22/ directory,229 If you want to activate Java support for the ZOO Kernel then you will have to use the 230 ``--with-java`` option and set the installation path of your Java SDK. For instance, 231 let's suppose that your Java SDK was installed in the /usr/lib/jvm/java-6-sun-1.6.0.22/ directory, 168 232 then you can use the following command: 169 233 … … 172 236 $ ./configure --with-java=/usr/lib/jvm/java-6-sun-1.6.0.22/ 173 237 174 This supposethat the include/linux and jre/lib/i386/client/ subdirectories exist in238 This assumes that the include/linux and jre/lib/i386/client/ subdirectories exist in 175 239 /usr/lib/jvm/java-6-sun-1.6.0.22/, include/linux contains the jni.h headers file and 176 240 jre/lib/i386/client/ contains the libjvm.so file. 177 241 178 Note that on MacOS X you only have to set macos as value for the "*--with-java*" option 179 to get the Java Support for ZOO-Kernel activated. So using the following command: 180 181 :: 182 183 $ ./configure --with-java=macos 242 .. note:: 243 With Mac OS X you only have to set ``macos`` as the value for the ``--with-java`` option 244 to activate Java support. For example: 245 246 :: 247 248 $ ./configure --with-java=macos 184 249 185 250 (Optional) JavaScript Support 186 251 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 187 252 188 If you want to activate the JavaScript Support for ZOO-Kernel then you will have to use189 the "*--with-js*"option. If you are using a "Debian-like" GNU/Linux distribution then190 dpkg will be used to detect if the required packages wasinstalled and you don't have to253 If you want to activate JavaScript support for the ZOO Kernel then you will have to use 254 the ``--with-js`` option. If you are using a "Debian-like" GNU/Linux distribution then 255 dpkg will be used to detect if the required packages are installed and you don't have to 191 256 specify anything here, so you can use the following command: 192 257 … … 195 260 $ ./configure --with-js 196 261 197 This supposethat js_api.h and libmozjs.so are found in default directories.198 199 If you geta custom installation of SpiderMonkey or you are not using a Debian packaging262 This assumes that js_api.h and libmozjs.so are found in default directories. 263 264 If you have a custom installation of SpiderMonkey or you are not using a Debian packaging 200 265 system, then you'll have to specify the directory where you installed it. For 201 instance, let suppose that you installed your SpiderMonkey in /usr, then you'll266 instance, let's suppose that you installed your SpiderMonkey in /usr, then you'll 202 267 have to use the following command: 203 268 … … 206 271 $ ./configure --with-js=/usr 207 272 208 This supposethat the /usr/include/js exists and contains the js_api.h headers file and273 This assumes that the /usr/include/js exists and contains the js_api.h headers file and 209 274 /usr/lib contains libmozjs.so file. 275 276 .. _win32: 277 278 OpenSUSE 279 ******** 210 280 211 281 WIN32
Note: See TracChangeset
for help on using the changeset viewer.
