From 0cdc4b706f3561a901b3d229e27b5f1590bcc130 Mon Sep 17 00:00:00 2001 From: knodlseder <> Date: Wed, 20 Jul 2011 21:52:22 +0000 Subject: [PATCH] updated for ctatools-00-02-04 --- ChangeLog | 10 +++++++++- NEWS | 18 ++++++++++-------- ctatools.pc.in | 4 ++-- doc/html/download.html | 22 +++++++++++++++------- doc/html/installation.html | 150 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------------------------- 5 files changed, 152 insertions(+), 52 deletions(-) diff --git a/ChangeLog b/ChangeLog index d1d713a..dfc650b 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,9 +1,17 @@ +2011-07-20 Juergen Knoedlseder + + * Version 0.2.4 released + ======================== + + Improve configure script + Add scripts for ctatools environment setting + 2011-07-09 Juergen Knoedlseder * Version 0.2.3 released ======================== - Improve configuration script + Improve configure script 2011-02-24 Juergen Knoedlseder diff --git a/NEWS b/NEWS index 5a34812..aba4145 100644 --- a/NEWS +++ b/NEWS @@ -1,8 +1,8 @@ -New Features and Important Changes in ctatools 00-02-03 +New Features and Important Changes in ctatools 00-02-04 Author(s) : Juergen Knoedlseder -July 9th, 2011 +July 20, 2011 1. Introduction @@ -12,12 +12,14 @@ This document briefly summarizes executable by executable the most important cha 2. Configuration ----------------- -Remove pkg-config usage from configure.ac as this introduced somas -on Mac OS X systems (by default there is no pkg-config on Mac OS X). - -Test for presence of Python.h and build Python binding only if the -file exists. This should resolve installation issues on systems that -do not have the Python development package installed. +The configuration script aborts now if no C++ compiler is found. + +Added ctatools-init.sh, ctatools-init.csh and ctatools-setup +scripts. They needed to be called when ctatools is installed +in a location that differs from GammaLib, so that the +environment is set up correctly also for this case. If ctatools +is in the same location as GammaLib, these scripts do not need +to be used. 3. Python interface diff --git a/ctatools.pc.in b/ctatools.pc.in index 81a3d26..877e526 100644 --- a/ctatools.pc.in +++ b/ctatools.pc.in @@ -6,9 +6,9 @@ includedir=${prefix}/include Name: ctatools Description: CTA science analysis tools URL: http://cta.irap.omp.eu/ctatools -Version: 0.2.3 +Version: 0.2.4 Requires: -Requires.private: GammaLib >= 0.4.9 +Requires.private: GammaLib >= 0.4.10 Conflicts: Cflags: -I${includedir}/ctatools Libs: -L${libdir} -lctatools diff --git a/doc/html/download.html b/doc/html/download.html index cf1ddbf..66f10e5 100644 --- a/doc/html/download.html +++ b/doc/html/download.html @@ -7,8 +7,8 @@

Download

-The latest ctatools release is ctatools-00-02-03 -(July 9, 2011).

+The latest ctatools release is ctatools-00-02-04 +(July 20, 2011).



Latest release

@@ -22,8 +22,12 @@ and gammalib versions.

gammalib -00-02-03 -00-04-09 +00-02-04 +00-04-10 + + +ChangeLog +ChangeLog @@ -40,15 +44,19 @@ and gammalib versions.

gammalib -00-02-01 -00-04-07 +00-02-03 +00-04-09 + + +00-02-01 +00-04-07

Last updated by: Jürgen -Knödlseder 9 July +Knödlseder 20 July 2011

\ No newline at end of file diff --git a/doc/html/installation.html b/doc/html/installation.html index bdb3f94..358a916 100644 --- a/doc/html/installation.html +++ b/doc/html/installation.html @@ -2,7 +2,8 @@ Installation - + +

Installation

@@ -10,19 +11,26 @@ GammaLib

-Step 2: Setup -environment +Step 2: +Setup +GammaLib environment

Step 3: Install ctatools

+

+Step 4: +Setup +ctatools environment +

Known Problems

Getting Help


Note: These installation instructions apply to -ctatools-00-02-03 or later. +ctatools-00-02-04 +or later.


Step @@ -38,17 +46,20 @@ follow the GammaLib installation instructions on

-

Step -2: Setup environment

+

Step +2: Setup GammaLib environment

Before -using GammaLib (and ctatools use GammaLib) you have to setup some +building and installing ctatools, you have to configure GammaLib by +setting up some environment variables. -This will be done automatically by an initialisation script that will -be installed in the bin -directory. Assuming that you have installed GammaLib in the default +This will be done automatically by an initialisation script that is +found in the bin +directory of the GammaLib directory (we call here "GammaLib +directory" the directory into which GammaLib has been +installed). Assuming that you have installed GammaLib in the default directory /usr/local/gamma -you need to add the following to your .bashrc +you need to add the following to your $HOME/.bashrc or $HOME/.profile script on a Linux machine: @@ -58,8 +69,8 @@ source $GAMMALIB/bin/gammalib-init.sh

If you use C shell or a variant then add the following to your -.cshrc -or .tcshrc +$HOME/.cshrc +or $HOME/.tcshrc script:

setenv GAMMALIB /usr/local/gamma
@@ -73,13 +84,13 @@ downloading the ctatools tarball, save it in an appropriate location (for example /usr/local/gamma/src), and type

-> tar xvfz ctatools-00-02-03.tar.gz +> tar xvfz ctatools-00-02-04.tar.gz

Step in the created directory using

-> cd ctatools +> cd ctatools-00-02-04

and build and install ctatools by typing

@@ -125,38 +136,109 @@ full list of configuration options can be found using

> ./configure --help


+
+

Step +4: Setup ctatools environment

+

If +ctatools have been installed in the same directory as GammaLib (which is +the default configuration for ctatools) you are done.

+
+

If +you decided to install ctatools in a different directory, you have to +configure ctatools by +setting up some +environment variables. +This will be done automatically by an initialisation script that is +found in the bin +directory of the directory into which ctatools has been installed. +Assuming that you have installed ctatools into +/usr/local/ctatools +you need to add the following to your $HOME/.bashrc +or $HOME/.profile +script on a Linux +machine: +

+

export CTATOOLS=/usr/local/ctatools
+source $CTATOOLS/bin/ctatools-init.sh +

+

If +you use C shell or a variant then add the following to your +$HOME/.cshrc +or $HOME/.tcshrc +script: +

+

setenv CTATOOLS /usr/local/ctatools
+source $CTATOOLS/bin/ctatools-init.csh

+
+

Known Problems

+Python +support +
+ctatools comes with Python wrappers so that all classes can be +directly used from Python. To compile-in Python support, ctatools +needs the Python.h +header file, which on many distributions is not +installed by default. +To make Python.h +available, install the Python developer package +in your distribution. Otherwise you will not be able to use ctatools +from Python. +

+
+

Mac OS X -
The Python development package is not installed as default on Mac -OS X, and consequently, the Python.h header file is missing that is -needed to compile in the Python bindings. The configure script should -recognise this fact and adjust the build procedure accordingly, but you +
+The Python development package is not installed as default on Mac +OS X, and consequently, the Python.h +header file is missing that is +needed to compile in the Python bindings. The configure +script recognises this fact and adjust the build procedure accordingly, +but you will not be able to use ctatools from Python. So better install the -Python development package before installing ctatools.

It +Python development package before installing ctatools.

+

It was also reported that adding of export -MACOSX_DEPLOYMENT_TARGET=10.6 to the .bashrc file was necessary one +MACOSX_DEPLOYMENT_TARGET=10.6 to the .bashrc +file was necessary one some Mac OS X 10.6 installations to make ctatools compile.
-

-

-Solaris
-ctatools has been compiled successfully on Solaris 2.10 using the Sun -Studio compiler. However, GammaLib symbols are -not globally exported due to a strage behaviour of the Sun Studio -compiler. This prevents for example GammaLib library from catching -its own exceptions and from registering models. Consequently, many -functionnalities will not work.

+

Solaris
-

Using -gcc (version 3.4.3), ctatools and GammaLib works correctly on Solaris -2.10, yet loading ctatools or GammaLib as a Python module fails. +Although ctatools builds on Solaris using the Sun compiler, there are +problems with global symbols in shared libraries and exception +catching, which prevents the FITS interface to work +correctly. ctatools has however been built and tested successfully +using the GNU +compiler, and this is the only build method that is currently +supported. +Problems have also been encountered when compiling cfitsio versions +more recent than 3.250. The problems have been reported to the cfitsio +developer team, and are likely to be solved in the future. For the +time being, it is recommended to use cfitsio version 3.250 on Solaris. +


+

OpenSolaris
+On OpenSolaris, the same problems concerning the SunStudio compiler +occur as for Solaris, and also here, the GNU compiler is the +recommended +tool to build ctatools. Also here, cfitsio version 3.250 is the +recommended library as more recent version feature relocation +problems. ctatools has been tested using gcc 4.3.2 on OpenSolaris +2009.06. Make sure to create the symbolic links +

+

ln -s /usr/bin/gcc4.3.2 /usr/bin/gcc
+ln -s /usr/bin/g++4.3.2 /usr/bin/g++

+

+which are not there by default to avoid excess warnings during +compilation.


+

Getting Help

@@ -167,7 +249,7 @@ ctatools should be submitted to

Last updated by: Jürgen -Knödlseder 9 July +Knödlseder 16 July 2011

\ No newline at end of file -- libgit2 0.21.4