Modules in this release include:
The installed code for psModule consists of header files and a binary library.
We recommend using the particular versions listed as compatibility tested, as that is the only versions of the external libraries tested to work well with psLib and psModule. Though it is quite possible that later versions of the libraries listed will also work, care must be taken when upgrading these libraries to verify that its functionality is compatible with the tested version.
If one has a login account on mhpcc.pan-starrs.org, direct CVS access is possible. Example of the commands required for direct CVS retrieval are as follows:
$ cvs -d:ext:USERNAME@mhpcc.pan-starrs.org:/data/panstarrs/cvsroot co -r RELEASEBRANCH psModulewhere:
The source should build using the configure script in the psModule directory. The recommended steps are:
$ cd psModule $ ./configure $ make $ make check $ make installUnless otherwise specified, the library is installed with PREFIX of the current directory.
If the code was retrieved from CVS, you will need to substitute 'autogen.sh' for 'configure' in above example.
Other configuration options, such as location of external libraries, are also available. To get a list of options, type the following in the top psModule directory.
$ configure --helpA likely option needed is '--with-pslib-config', which specifies the location of the configuration script for psLib. By default, configure searches for it using PATH, but that is not always sufficient.
$ make install
The required CFLAG options for the compiler stage of code that uses psModule can be obtained via 'psmodule-config --cflags'. This outputs the cc options that supplies include path(s) required to find the psModule headers.
The required linking options, can be obtained via 'psmodule-config --libs'. This outputs the ld options that supplies the library paths and files required to link to the psModule library.
Note: psmodule-config usage above refers to the install locations of the library.
$ cd psModule $ make docsThis places documentation in PREFIX/docs.
Also, a prebuilt set of code documentation for both the releases and last CVS snapshot can be found at: