Commit 823885d5c7bed5cb83863145a65114361fd98e16
1 parent
f17d37df
Updated installation documentation, including hint on how to solve cfitsio not found problem.
Showing
1 changed file
with
53 additions
and
23 deletions
doc/source/installation.rst
| ... | ... | @@ -5,8 +5,8 @@ Installation |
| 5 | 5 | .. note :: |
| 6 | 6 | |
| 7 | 7 | These installation instructions apply to gammalib-00-04-10 and |
| 8 | - later. gammalib-00-04-10 has been built, installed and tested | |
| 9 | - successfully on Debian, Ubuntu, Mandriva, OpenSUSE, Scientific Linux, | |
| 8 | + later. gammalib-00-04-10 has been built, installed and tested | |
| 9 | + successfully on Debian, Ubuntu, Mandriva, OpenSUSE, Scientific Linux, | |
| 10 | 10 | CentOS, gentoo, Mac OS X, FreeBSD, and OpenSolaris (using gcc), so |
| 11 | 11 | hopefully it also installs on your distribution. In case you encounter |
| 12 | 12 | problems, please post a report on the bug tracker or send an e-mail to the |
| ... | ... | @@ -109,7 +109,7 @@ GammaLib should be tested by typing:: |
| 109 | 109 | This will execute an extensive testing suite that should terminate with :: |
| 110 | 110 | |
| 111 | 111 | =================== |
| 112 | - All 17 tests passed | |
| 112 | + All 20 tests passed | |
| 113 | 113 | =================== |
| 114 | 114 | |
| 115 | 115 | Eventually, loading the shared cfitsio and/or readline libraries may |
| ... | ... | @@ -131,7 +131,7 @@ Installing GammaLib |
| 131 | 131 | |
| 132 | 132 | Install GammaLib by typing :: |
| 133 | 133 | |
| 134 | - $ make install | |
| 134 | + $ make install | |
| 135 | 135 | |
| 136 | 136 | at the operating system prompt. |
| 137 | 137 | |
| ... | ... | @@ -157,27 +157,42 @@ If you use C shell or a variant then add the following to your |
| 157 | 157 | Installing documentation |
| 158 | 158 | ------------------------ |
| 159 | 159 | |
| 160 | -The GammaLib web pages are shipped together with the source code and | |
| 160 | +The GammaLib documentation is shipped together with the source code and | |
| 161 | 161 | will be installed in the directory ``$(prefix)/share/doc/gammalib/html``, |
| 162 | 162 | where ``$(prefix)`` is the installation base path, by default |
| 163 | -``/usr/local/gamma``. | |
| 163 | +``/usr/local/gamma``. This comprises user documentation and code | |
| 164 | +documentation. | |
| 165 | + | |
| 166 | +To build the user documentation you need the Sphinx reStructuredText | |
| 167 | +documentation generator installed | |
| 168 | +(see `http://sphinx-doc.org/rest.html <http://sphinx-doc.org/rest.html>`_ | |
| 169 | +for more information). | |
| 170 | +Code documentation is based on Doxygen, which also needs to be installed | |
| 171 | +on your system | |
| 172 | +(see `http://dogygen.org <http://doxygen.org>`_ to download and install | |
| 173 | +the Doxygen package). | |
| 174 | +Doxygen will scan the source files for code annotations, and compiles a | |
| 175 | +complete documentation of the implemented C++ classes in a set of html | |
| 176 | +pages. In addition, it will create a set of man files that can be used by | |
| 177 | +the man command. | |
| 178 | + | |
| 179 | +To build and install all documentation, type the following:: | |
| 180 | + | |
| 181 | + $ ./configure | |
| 182 | + $ make doc | |
| 183 | + $ make install | |
| 184 | + | |
| 185 | +To build only user documentation, type:: | |
| 164 | 186 | |
| 165 | -For developers, a more detailed documentation can be built from the | |
| 166 | -source code using Doxygen. Doxygen will scan the source files for code | |
| 167 | -annotations, and compiles a complete documentation of the implemented | |
| 168 | -C++ classes in a set of www pages. In addition, it will create a set of | |
| 169 | -man files that can be used by the man command. If you have not installed | |
| 170 | -Doxygen on your machine, but you need the development documentation, | |
| 171 | -please visit | |
| 172 | -`http://dogygen.org <http://doxygen.org>`_ | |
| 173 | -to download and install the Doxygen package. | |
| 187 | + $ ./configure | |
| 188 | + $ make sphinx | |
| 189 | + $ make install | |
| 174 | 190 | |
| 175 | -Once Doxygen is install, type the following to build and to install the | |
| 176 | -Doxygen documentation:: | |
| 191 | +and to build only Doxygen documentation, type:: | |
| 177 | 192 | |
| 178 | 193 | $ ./configure |
| 179 | 194 | $ make doxygen |
| 180 | - $ make doxygen-install | |
| 195 | + $ make install | |
| 181 | 196 | |
| 182 | 197 | The Doxygen documentation will be installed into |
| 183 | 198 | ``$(prefix)/share/doc/gammalib/html/doxygen`` and can be browsed using a |
| ... | ... | @@ -192,6 +207,20 @@ and you should see the documentation for the GObservations C++ class. |
| 192 | 207 | Known Problems |
| 193 | 208 | -------------- |
| 194 | 209 | |
| 210 | +* cfitsio library not found | |
| 211 | + Occasionally it may happen that the cfitsio library is not found when | |
| 212 | + configuring GammaLib. This will result is lots of errors during the | |
| 213 | + unit tests. If you are sure that cfitsio is installed, but the path | |
| 214 | + where the library and the path where the fitsio.h reside are | |
| 215 | + non-standard, you may add the paths explicitly during configuration | |
| 216 | + using:: | |
| 217 | + | |
| 218 | + $ ./configure LDFLAGS='-L/path/to/cftsio/library' CPPFLAGS='-I/path/to/fitsio.h/header' | |
| 219 | + | |
| 220 | + The same logic applies for finding the readline and ncurses libraries, | |
| 221 | + thought these libraries are not manadatory for getting the full | |
| 222 | + GammaLib functionnalities. | |
| 223 | + | |
| 195 | 224 | * Python support |
| 196 | 225 | GammaLib comes with Python wrappers so that all classes can be directly |
| 197 | 226 | used from Python. To compile-in Python support, GammaLib needs the |
| ... | ... | @@ -206,12 +235,12 @@ Known Problems |
| 206 | 235 | compile in the Python bindings. The configure script recognises this |
| 207 | 236 | fact and adjust the build procedure accordingly, but you will not be |
| 208 | 237 | able to use GammaLib from Python. So better install the Python |
| 209 | - development package before installing GammaLib (see above). | |
| 238 | + development package before installing GammaLib (see above). | |
| 210 | 239 | |
| 211 | 240 | * Solaris |
| 212 | - Although GammaLib builds on Solaris using the Sun compiler, there are | |
| 241 | + Although GammaLib builds on Solaris using the Sun compiler, there are | |
| 213 | 242 | problems with global symbols in shared libraries and exception catching, |
| 214 | - which prevents the FITS interface to work correctly. GammaLib has | |
| 243 | + which prevents the FITS interface to work correctly. GammaLib has | |
| 215 | 244 | however been built and tested successfully using the GNU compiler, and |
| 216 | 245 | this is the only build method that is currently supported. Problems have |
| 217 | 246 | also been encountered when compiling cfitsio versions more recent than |
| ... | ... | @@ -222,9 +251,9 @@ Known Problems |
| 222 | 251 | * OpenSolaris |
| 223 | 252 | On OpenSolaris, the same problems concerning the SunStudio compiler |
| 224 | 253 | occur as for Solaris, and also here, the GNU compiler is the recommended |
| 225 | - tool to build GammaLib. Also here, cfitsio version 3.250 is the | |
| 254 | + tool to build GammaLib. Also here, cfitsio version 3.250 is the | |
| 226 | 255 | recommended library as more recent version feature relocation |
| 227 | - problems. GammaLib has been tested using gcc 4.3.2 on OpenSolaris | |
| 256 | + problems. GammaLib has been tested using gcc 4.3.2 on OpenSolaris | |
| 228 | 257 | 2009.06. Make sure to create the symbolic links :: |
| 229 | 258 | |
| 230 | 259 | $ ln -s /usr/bin/gcc4.3.2 /usr/bin/gcc |
| ... | ... | @@ -233,6 +262,7 @@ Known Problems |
| 233 | 262 | which are not there by default to avoid excess warnings during |
| 234 | 263 | compilation. |
| 235 | 264 | |
| 265 | + | |
| 236 | 266 | Getting Help |
| 237 | 267 | ------------ |
| 238 | 268 | ... | ... |