UCAR/EOL/RAL CIDD display software ================================== README for INSTALLING a BINARY distribution. Web documentation ----------------- For full details see: http://www.ral.ucar.edu/CIDD LINUX setup ----------- Radx is primarily intended to run on LINUX and OSX. Most good, up-to date LINUX distributions should work. Recommended OSs are: Ubuntu Debian Fedora Scientific Linux Mac OSX Required packages for compiling: tcsh shell perl shell python shell Downloading ----------- For 64-bit systems, the cidd binary release will be named: cidd-yyyymmdd.x86_64.tgz For 32-bit systems, the cidd binary release will be named: cidd-yyyymmdd.i686.tgz where yyyymmdd is the date of the distribution. Download this file from: ftp.rap.ucar.edu/pub/titan/cidd Previous releases can be found in: ftp.rap.ucar.edu/pub/titan/cidd/previous_releases Download the file into a tmp area. For example: /tmp/cidd_dist and install from there. However, any suitable directory can be used for this purpose. Un-tarring the file ------------------- Use the command tar xvfz cidd-yyyymmdd.x86_64.tgz (64-bit systems) or tar xvfz cidd-yyyymmdd.i686.tgz (32-bit systems) to un-tar the distribution into the current directory. yyyymmdd should be substituded with the actual date on the file. Then, cd into the directory: cd cidd-yyyymmdd.x86_64 or cd cidd-yyyymmdd.i686 Installing ---------- You will probably need to be root for this step, unless you install in your user area. By default, the binaries will be installed in /usr/local/bin. You can specify an alternative. install_bin_release will install in /usr/local/bin. install_bin_release /opt/local will install in /opt/local/bin. The support dynamic libraries will be found in: ..../bin/cidd_runtime_libs i.e. in a subdirectory of the bin directory. Sample configuration files. --------------------------- The project files will be in: /usr/local/projects/cidd/projDir or /opt/local/projects/cidd/projDir or relative to wherever you performed the install. The symbolic link: ~/projDir will point to the project files. Installing 32-bit compatibility files ------------------------------------- CIDD is compiled in 32-bit compatibility mode. Therefore the 32-bit runtime libs must be installed on the host. On a RedHat-type machine (RedHat, Fedora, CentOS, Scientific Limux) you need to use yum. # To install the equivalent of ia32-libs, you can do the following: yum -y install glibc-devel.i686 yum -y install libX11-devel.i686 yum -y install libXext-devel.i686 yum -y install libjpeg-devel.i686 yum -y install libpng-devel.i686 yum -y install libstdc++-devel.i686 yum -y install libtiff-devel.i686 or for a complete list: yum -y install --skip-broken glibc.i686 arts.i686 audiofile.i686 bzip2-libs.i686 cairo.i686 cyrus-sasl-lib.i686 dbus-libs.i686 directfb.i686 esound-libs.i686 fltk.i686 freeglut.i686 gtk2.i686 hal-libs.i686 imlib.i686 lcms-libs.i686 lesstif.i686 libacl.i686 libao.i686 libattr.i686 libcap.i686 libdrm.i686 libexif.i686 libgnomecanvas.i686 libICE.i686 libieee1284.i686 libsigc++20.i686 libSM.i686 libtool-ltdl.i686 libusb.i686 libwmf.i686 libwmf-lite.i686 libX11.i686 libXau.i686 libXaw.i686 libXcomposite.i686 libXdamage.i686 libXdmcp.i686 libXext.i686 libXfixes.i686 libxkbfile.i686 libxml2.i686 libXmu.i686 libXp.i686 libXpm.i686 libXScrnSaver.i686 libxslt.i686 libXt.i686 libXtst.i686 libXv.i686 libXxf86vm.i686 lzo.i686 mesa-libGL.i686 mesa-libGLU.i686 nas-libs.i686 nss_ldap.i686 cdk.i686 openldap.i686 pam.i686 popt.i686 pulseaudio-libs.i686 sane-backends-libs-gphoto2.i686 sane-backends-libs.i686 SDL.i686 svgalib.i686 unixODBC.i686 zlib.i686 compat-expat1.i686 compat-libstdc++-33.i686 openal-soft.i686 alsa-oss-libs.i686 redhat-lsb.i686 alsa-plugins-pulseaudio.i686 alsa-plugins-oss.i686 alsa-lib.i686 nspluginwrapper.i686 libXv.i686 libXScrnSaver.i686 qt.i686 qt-x11.i686 pulseaudio-libs.i686 pulseaudio-libs-glib2.i686 alsa-plugins-pulseaudio.i686 On Debian hosts, you need to install: ia32-libs-dev and 32-bit versions of stdc++, libc, libpng, libz Also see: http://www.howtodoityourself.org/how-to-fix-libld-linux-so-2-bad-elf-interpreter-no-such-file-or-directory.html