The following components should be installed on your machine:
Package | Comment | Max OS X | Debian Linux |
---|---|---|---|
Subversion client | Fink | ||
C/C++ compiler | |||
Fortran compiler | |||
Flex | Fink | ||
Bison | Fink | ||
LAPACK | Fink | ||
BLAS | Fink | ||
SWIG | required for PLplot | ||
Python | application and development files | ||
gawk | v3.1.6 or higher | ||
bzip2 | gave problems when missing on a debian system | install libbz2-dev |
The following external components are required but come as part of the provided distribution:
Finally there are a number of (more or less) optional components, which depend on the presence of the following packages:
FFTW
!)All the source code for the CR-Tools is available through the Subversion repository of the User Software Group; in order to obtain a working copy run the following command:
svn co http://usg.lofar.org/svn/code/trunk lofarsoft
There is a build script available, which will go through the list of required external components – and finally build the CR-Tools themselves. The script can be run in two different ways:
cd lofarsoft export LOFARSOFT=`pwd` . devel_common/scripts/init.sh
cd $LOFARSOFT/build ./bootstrap make cr
Notes:
make clean_build
cd usg/build cmake ../src/CR-Tools make install
Though of course some details may look different on your system, you should be receiving an output like this:
-- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Check size of void* -- Check size of void* - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- [CR] Configuration to use CASA ... -- [CR] Installation area located. -- CMAKE_SYSTEM .......... : Linux-2.6.4-52-smp -- CMAKE_SYSTEM_PROCESSOR : i686 -- CMAKE_SYSTEM_64BIT .....: 0 -- CMAKE_SYSTEM_BIG_ENDIAN : -- BLITZ ................. : TRUE -- CASA .................. : TRUE -- CASACORE .............. : FALSE -- CFITSIO ............... : TRUE -- FFTW3 ................. : TRUE -- LAPACK ................ : TRUE -- PGPLOT ................ : TRUE -- ROOT .................. : TRUE -- WCSLIB ................ : TRUE -- Configuring done -- Generating done -- Build files have been written to: /opt/local/lofarsoft/build/cr
Depending on what is already installed on your system, you will get a number of warnings or error messages stating that required external packages are missing; a common scenario e.g. is, that you are missing CFITSIO.
The list of configuration options (e.g. build the tools collection with Glish support) can be found at the optional build parameters page.
(Glish support is needed to build the Glish clients needed for the “old” lopestools. It requires a working CASA installation that was installed seperately.)
Add the location of the new executables to your PATH variable:
set path = ( $path <LOFARSOFT>/release/bin )
In this LOFARSOFT should point to base of your working copy of the USG code tree.
.profile
or .bashrc
file: export LOFARSOFT=<path to root working copy> . $LOFARSOFT/devel_common/scripts/init.sh
Even though it is not expected that the init instruction will be undergoing a lot of changes, this is the securest method by which to catch changes if they take place.
If you don't have matplotlib or scipy installed you can install them from the repository:
cd $LOFARSOFT/build make matplotlib make scipy