Current CPL Release
The following table provides the download links for the latest offical release of the CPL source packages, the documentation, and the Esorex tool. As a convenience the source packages of the third-party libraries which were used to verify this CPL release are also available from the table below.
Previous CPL releases are available here.
CPL source code distribution
Note: should be used with CFITSIO 3.350 or later
|cpl-user-manual_6.0.pdf||CPL User Manual (outdated!)|
CPL Reference Manual (PDF)
The on-line version of the manual is available here.
ESO Recipe Execution tool
Note: for CPL 6.5 or later use esorex 3.11 or newer.
|cfitsio3360.tar.gz||CFITSIO library from NASA, version 3.360||610f830a17fd78cf80e47e96254b5e5c|
|wcslib-4.24.tar.bz2||WCSLIB library of M. Calabretta, version 4.24||10f44010cd4a47b63a5180a215386ab9|
|fftw-3.3.4.tar.gz||FFTW library, version 3.3.4||2edab8c06b24feeb3b82bbb3ebf3e7b3|
Note: The integrity of the downloaded packages may be verified using the MD5 signatures from the table (see here for details).
Changes in CPL 7.0
This release addresses a small number of corrections in the API which were known issues since some time already. This was done in view of some bigger (internal) changes planned for the next releases. It, essentially, provides the same feature set as the previous CPL 6.6.1 release.
Previous CPL Releases
The last releases of the CPL source packages can be accessed through the links in the table. In addition the third-party library packages which were used and tested with the individual releases are also available.
The CPL is supported on the VLT target platforms running the following operating systems:
- Scientific Linux 6.3 (64bit)
However, it is intended that the CPL builds also on other flavors of Linux and Unix systems, and it is known that the CPL has been successfully built on recent Linux distributions (Fedora, OpenSUSE, Debian Ubuntu, and others), as well as on Mac OS X platforms.
The following tools are needed to build the CPL from the source distribution:
- GNU C/C++ compiler (version 4.4 or newer)
- GNU make utility
- GNU tar and gzip utilities.
- Java Development Kit version 1.6 or newer (optional, only needed if Gasgano support is required)
Third-party libraries used in CPL
In addition to the development tools for building the CPL, it depends on a small number of external library packages:
Since CPL uses CFITSIO to access FITS files, it requires an appropriate CFITSIO installation
to be available on the target system.
CPL also delegates some specific functionality, namely Fourier transforms and world coordinate system transformations to dedicated, specialized libraries. In case this functionality is not needed, CPL can be build and used without having FFTW and/or WCSLIB installed. However, in general this is not recommended, since Fourier transforms an world coordinate system handling are then not available in CPL!
Workarounds for Mac OS X users:
The following list provides hints to work around some known issues on Mac OS X:
- Compilation error on Mac OS X 10.8 (or newer): version 6.1.1 of CPL
cannot be built with the default C compiler (clang),
because of unsupported C99 features. The current CPL release requires a
full GCC installation which may be obtained from
MacPorts for instance.
This issue is fixed in CPL version 6.2!
- Compilation error because of not finding the javah executable: to
avoid this the environment variable
JAVA_HOMEwhich points to the JDK installation should be set to:
configurescript is executed. If this does not succeed try the following setting:
Please note that support for Mac OS X can only be provided on a best effort basis!
Installing and using the CPL
Please refer to the README file in the CPL distribution for details about how to install and use the software. A detailed description of the library is provided in the CPL User Manual (see the link in the list of "downloads" above). Additional documentation is available from the CPL Documentation page.
Checking the Package IntegrityThe integrity of the downloaded packages may be verified using the MD5 files which are available from the current release download table. They contain the MD5 fingerprint of the corresponding package. To verify the package, get the MD5 file by saving the MD5 sum link, put it into the same directory as the package, and execute the command:
md5sum -c <md5file>