Appendix C. Platform Notes.
 
                
The ECP package (with Qt version 4.3.0,
4 .3.1 and Qwt version 5.0.2) was
tested extensively under both Windows XP and Linux Fedora
Core 7 and for a short time under Mac OS X.
 
 
 
 I. Recommendations on installation:
 
  
   
 Upload software from the links given 
on Download page.
 
  
    
Windows 
XP users must have MinGw, Qt and Qwt packages 
installed on their machine.
 
    
  
 
  
 
  
 
  
 
  
 
  
   
  
 
  
   
  
 
  
 
  
 
   
    
 
 
  
 
  
 
  
 
  
 
   The 
packages mingw-runtime, w32api, binutils, gcc-core, gcc-g++ and mingw32-make are 
the minimal requirements for MinGw installation. For such an
installation, uncompress the archives of mingw-runtime, w32api,  binutils,
gcc-core, gcc-g++ and mingw32-make into <MinGWInstalDirectory>.
 Locate mingw32-make and other MinGwt tools by adding <MinGWInstalDirectory>\bin
 in the environment variable PATH, i.e., invoke "Control Panel->System->Advanced->Environment 
variables"; invoke “Edit”, if PATH exists, and add <MinGWInstalDirectory>\bin 
into Variable value separating it from the other values with 
semicolon; if PATH does not exist, invoke “New” and type in PATH into Variable name and <MinGWInstalDirectory>\bin into Variable value. 
     Uncompress 
the Qt archive into <QtInstallDirectory>. Locate qmake, moc and 
other Qt tools by adding <QtInstallDirectory>\bin in the environment 
variable PATH, i.e., invoke "Control Panel->System->Advanced->Environment
 variables"; invoke “Edit” and add <QtInstallDirectory>\bin into Variable value separating it from the other values with semicolon. 
Build the Qt library by executing from the Command Prompt ("All Programs->Accessories->Command 
Prompt") the following commands
     cd  <QtInstallDirectory>
     configure -platform win32-g++ -release -static -no-qt3support
     make
   Unzip Qwt archive into <QwtInstallDirectory>\temp . Edit 
qwtconfig.pri by commenting the following lines with # :
     #CONFIG     += QwtDll 
     #CONFIG     += QwtSVGItem
     #CONFIG     += QwtMathML
     #CONFIG     += QwtDesigner
 and changing the win32 installbase as shown below
   win32 {
         INSTALLBASE    = <QwtInstallDirectory>
     }
 Build Qwt by executing from the Command Prompt the following 
commands :
     cd <QwtInstallDirectory>\temp
     qmake qwt.pro
     make
     make install
 
 Unix/X11 (Linux, Sun Solaris, etc ) and Mac OS X users must have Qt and Qwt packages installed on their 
machine
 
 Unpack the Qt archive by performing the following commands
 cd /tmp
     gunzip qt-x11-opensource-src-x.x.x.tar.gz  
     tar xvf qt-x11-opensource-src-x.x.x.tar
 where x.x.x. is the Qt version number.  By default, 
Qt is configured for installation in the  /usr/local/Trolltech/Qt-x.x.x.
 Build Qt by executing the following commands :
     cd  /tmp/qt-x11-opensource-src-x.x.x
     configure -platform linux-g++ -release -static -no-qt3support
     make
     make install
 (If you need to reconfigure and rebuild Qt from the same location, ensure 
that all traces of the previous configuration are removed by entering the 
build directory and typing
     make confclean
 before running the configure script again. Then 
make .)
 Locate qmake, moc and other Qt tools in the environment variable PATH. If the shell is bash add the following lines to .profile:
     PATH=/usr/local/Trolltech/Qt-x.x.x /bin:$PATH
     export PATH 
 If the shell is csh or tcsh add the following lines to .login and/or to
.cshrc  or .tcshrc , correspondingly: 
     setenv PATH /usr/local/Trolltech/Qt-x.x.x /bin:$PATH
 In case of some other different shell, modify your environment variables 
accordingly.    Unpack the Qwt archive 
by performing the following commands :
     cd /tmp
 
    bzip2 -d  qwt-x.x.x.tar.bz2 
     tar xvf qwt-x.x.x.tar
 here x.x.x. is the Qwt version number.  By default, 
Qwt is configured for installation in the /usr/local/qwt/x.x.x.
 Edit qwtconfig.pri by commenting the following lines with # :
     #CONFIG     += QwtDll
     #CONFIG     += QwtSVGItem
     #CONFIG     += QwtMathML
     #CONFIG     += QwtDesigner
 and changing the unix installbase as shown below
     unix {
         INSTALLBASE    =  
/usr/local/qwt/x.x.x 
     }
 Build Qwt by executing the following commands
     cd /temp/qwt-x.x.x
     qmake qwt.pro
     make
     make install  
 
  
 
 
 
  
 
  
 
 
  
 
Storage 
of settings
     Users normally expect an application to 
remember its settings (window sizes and positions, options, etc.) across sessions.
This information is often stored in the system registry on Windows, and in
XML preferences files on Mac OS X. On Unix systems, in the absence of a standard,
many applications (including the KDE applications) use INI text files. 
    On Windows, NativeFormat settings are
stored in the following registry paths: 
     HKEY_CURRENT_USER\Software\mitp.ru
    On Linux systems, if the file format is 
NativeFormat, the following files are used by default: 
    $HOME/.config/mitp.ru
 
   
   
  
     While installing CompiCat 
program its shortcut is being created on desktop automatically, which is convenient.
It allows invoking programs quickly without using some Files Manager for
searching the program.
 
  
 
 Windows:
 
  
    Open Windows Explorer and
browse to directory ....\ecp\bin, find file named "compicat.exe" and click
the right button. Invoke popup menu items "Send To -> Desktop(create shortcut)".
 Click the right mouse button on the created shortcut. Invoke popup
menu item "Properties". A dialog box "CompiCat Properties" will appear.
Click "Change Icon" on "Shortcut" tab and browse to directory ...\ecp\ref 
and choose "icon.ico".
 
  
 
 KDE Windows Manager:
 
 
    Click right mouse button 
on a free space of desktop. Click popup menu items "Create New -> Link 
to Application". Type the program name “CompiCat” on General tab. Then change 
application icon: click on the existing icon; check "Other icons", browse 
to directory ..../ecp/ref and choose "icon.png". Then go to Application tab, 
click "Browse" and browse to directory ..../ecp/bin, choose the file named 
"compicat". 
 
  
   
 
      One of the most 
convenient aspects of a windows system is its ability to automatically link 
a data file with its application. CompiCat program file associations are being
created on installation automatically. When you click on an icon of a file
with earthquake catalog in the standard format (i.e., with filename extension
"csf"), a Files Manager will start CompiCat program and load the catalog
automatically, so that you begin working on it.