Installation of the "o" packages

Installation

The brute list of the "o" packages is :

Co : utilities over C libraries, omake, osh interpreter, type manager,...
Xx : utilities over Xt, X11.
Wo : the widget manager.
HTMLo : html widget from mosaic-2.6.
W3o : www library from mosaic-2.6.
Ho : "o" histograms, tuples.
GLo : an OpenGL implementation with X11, PostScript drivers.
Go : a graphic database over OpenGL.
Xo : widgets such as XoCamera, XoPlotter, XoMosaic.
Xz : HPLOT widget.
G3o : graphic for GEANT3.

To ease installation, the "o" packages are distributed by "groups" matching some standard environments. These groups are :

WoXm : the Wo widget manager knowing the MOTIF widget set.
WoXoXm : the Wo widget manager knowing the MOTIF widget set plus the "o" graphic over MOTIF.
WoXoXaw : the Wo widget manager knowing the Athena widget set plus the "o" graphic over Athena. This group is well adapted for a Linux environment that does not have Motif.
WoXoXmCERN : same as WoXoXm plus bindings to CERN libraries. It needs a FORTRAN compiler. This group is well adapted to a classic HEP environment.

To install the "o" packages an ANSI C or C++ compiler is required. All the code, though written in ANSI C, is compilable with C++.

Common installation problems are:

You try to compile with a non ANSI C compiler (exa: on SunOS).
The C include files are not ANSI (oftenly : time.h, ctype.h, signal.h).
You believe that MOTIF or ATHENA is installed on your station but it is not ; then compiler does not find the MOTIF or ATHENA include files (Xm.h,...).
The include files (C, MOTIF, X11) are not compilable with C++.

If you are in the upper situation contact your system manager.

Installation UNIX

     UNIX> mkdir <...>/OPACS
     UNIX> cd    <...>/OPACS
     UNIX> ftp ftp.lal.in2p3.fr
     anonymous
     user name
     ftp> cd pub/OPACS/v3
     ftp> bin
     ftp> get WoXm.tar.Z        # Wo widget manager knowing the MOTIF widget set.
    (ftp> get WoXoXm.tar.Z      # Wo widget manager knowing the MOTIF widget set
                                # plus the "o" graphic over MOTIF widget set.)
    (ftp> get WoXoXaw.tar.Z     # Wo widget manager knowing the Xaw widget set
                                # plus the "o" graphic over Athena widget set. 
                                # Adapted for Linux.)
    (ftp> get WoXoXmCERN.tar.Z  # Same as WoXm plus bindings to CERN libraries.
                                # Need a FORTRAN compiler and CERN libraries.)
     ftp> quit
     UNIX> uncompress WoXm.tar.Z
     UNIX> tar xvf WoXm.tar
    (UNIX> rm WoXm.tar)
     UNIX> cd OPACS/v3
     UNIX> emacs setup.csh      #  You have to edit the proposed setup files to
    (UNIX> emacs setup.sh)      # set correctly the "root" directory variable.
                                #  If you expect to reconstruct the OPACS with
                                # some external packages, like LAL/Ci, LAL/Cm, 
                                # CERNLIBS ; change the specific environment
                                # variables that permit to use them.
      csh> source setup.csh     #  To set your "o" environment. 
    (  sh> . setup.sh )
     UNIX> (g)make              #  To build the group in the `uname` config.
                                #  Look the head of "Makefile" file to have example
                                # of more complete commands.

The compilation "configs" are defined in the files :

     Co/v3/mgr/Config.mk
   ( W3o/v3/mgr/Config.mk   )  
   ( HTMLo/v3/mgr/Config.mk )

If the existing "configs" do not match your environment, edit these files. Existing configs are :

OSF1 HP-UX ULTRIX Linux AIX IRIX (not tested yet) SunOS (not tested yet) insure Linux-gxx

See the below "General considerations" for more.

Installation_NT

The "o" packages have been ported on Windows/NT over the X11 environment DEC/eXcursion.

Being on Windows, get a NT "command prompt" by double clicking in :

     "Program manager/Main/Command prompt".

Then type :

     NT> mkdir <...>\OPACS
     NT> cd    <...>\OPACS
     NT> ftp ftp.lal.in2p3.fr
     anonymous
     user name
     ftp> cd pub/OPACS/v3
     ftp> bin
     ftp> get WoXm.taZ        # Wo widget manager knowing the MOTIF widget set.
    (ftp> get WoXoXm.taZ      # Wo widget manager knowing the MOTIF widget set
                              # plus the "o" graphic over MOTIF widget set.)
    (ftp> get WoXoXaw.taZ     # Wo widget manager knowing the Xaw widget set
                              # plus the "o" graphic over Athena widget set. 
                              # Adapted for Linux.)
    (ftp> get WoXoXmCERN.taZ  # Same as WoXm plus bindings to CERN libraries.
                              # Need a FORTRAN compiler and CERN libraries.)
     ftp> quit

Use the interactive WinZip facility to decompress and extract the files. WinZip can be launched by double clicking on the taZ file from the "File manager". The first double click on the taZ file will produce a tar file. A second double clicking on the tar file will extract the files.

    (NT> delete WoXm.tar)
    (NT> delete WoXm.taZ)
     NT> cd OPACS/v3
     NT> edit setup.bat         #  You have to edit the proposed setup files to
                                # set correctly the "root" directory variable.
                                #  If you expect to reconstruct the OPACS with
                                # some external packages, like LAL/Ci, LAL/Cm, 
                                # CERNLIBS ; change the specific environment
                                # variables that permit to use them.
     NT> call setup.bat         # To set your "o" environment.
     NT> nmake /f NMake         # To build the group in the "NT" config.
                                # Look the head of "NMake" file to have example
                                # of more complete commands.

The compilation "configs" are defined in the files :

     Co\v3\mgr\Config.nmk
   ( W3o\v3\mgr\Config.nmk   )  
   ( HTMLo\v3\mgr\Config.nmk )

If the existing "configs" do not match your environment, edit these files. Existing configs are :

     NT
     NTD     (to compile in debug mode)

See the below "General considerations" for more.

Installation_VMS

The "o" packages has been ported on VAX/VMS and ALPHA/VMS.

     VMS$ create/dir  disk:[<...>.OPACS]
     VMS$ set def disk:[<...>.OPACS]
     VMS$ ftp ftp.lal.in2p3.fr
     anonymous
     user name
     ftp> cd pub/OPACS/v3
     ftp> bin
     ftp> get WoXm.tar_Z        # Wo widget manager knowing the MOTIF widget set.
    (ftp> get WoXoXm.tar_Z      # Wo widget manager knowing the MOTIF widget set
                                # plus the "o" graphic over MOTIF widget set.)
    (ftp> get WoXoXaw.tar_Z     # Wo widget manager knowing the Xaw widget set
                                # plus the "o" graphic over Athena widget set. 
                                # Adapted for Linux.)
    (ftp> get WoXoXmCERN.tar_Z  # Same as WoXm plus bindings to CERN libraries.
                                # Need a FORTRAN compiler and CERN libraries.)
     ftp> cd Alpha
    (ftp> cd VAX)
     ftp> get compress.exe
     ftp> get vmstar.exe
     ftp> quit
     VMS$ compress == "$disk:[<...>.OPACS]compress
     VMS$ vmstar   == "$disk:[<...>.OPACS]vmstar
     VMS$ compress -d WoXm.tar_Z
     VMS$ vmstar xvf WoXm.tar
    (VMS$ del WoXm.tar;*)
     VMS$ set def [.OPACS.v3]
     VMS$ edit setup.com        #  You have to edit the proposed setup files to
                                # set correctly the "root" directory variable.
                                #  If you expect to reconstruct the OPACS with
                                # some external packages, like LAL/Ci, LAL/Cm, 
                                # CERNLIBS ; change the specific environment
                                # variables that permit to use them.
     VMS$ @setup.com                   # To set your "o" environment.
     VMS$ mms                          # To build the "Wo" group in the ALPHA config.
                                       # Look the head of "descrip.mms" file to have example
                                       # of more complete commands.
    (VMS$ mms/macros=(CONFIG=VAX)      # To build the group in the VAX config.)

The compilation "configs" are defined in the files :

     [OPACS.Co.v3.mgr]Config.mk
   ( [OPACS.W3o.v3.mgr]Config.mk   )  
   ( [OPACS.HTMLo.v3.mgr]Config.mk )

If the existing "configs" do not match your environment, edit these files. Existing configs are :

     ALPHA
     VAX

See the below "General considerations" for more.

General considerations

If using any other none "o" packages like CERN libraries, or LAL Ci, Cm that are not in a "standard" place, edit the OPACS/v3/setup files to set the "root" directory variables that say where these packages are located.

Some packages could be declared to Wo (like Xaw, tcl,...). This is done in the Wo/v3/mgr/Make.odb file. The "has" property of the "Make" object controls the declared packages. Change this property according to examples. Run the "omake" tool that will regenerate the new Wo "This.mk" makefile :

     UNIX> cd <...>/Wo/v3/mgr
    (NT>   cd <...>\Wo\v3\mgr)
    (VMS$  set def disk:[<...>.Wo.v3.mgr])
     UNIX> vi Make.odb
    (NT>   edit Make.odb)
    (VMS$  edit Make.odb)
     UNIX> omake -make
    (NT>   omake -make)
    (VMS$  omake -make)

or :

     UNIX> omake -all
    (NT>   omake -all)
    (VMS$  omake -all)

to generate also This.nmk and This.mms for NT and VMS. The alias "omake" is defined in the OPACS/v3/setup files. Note that a "Make.odb" exists for each "o" package. For example, in the same way that above, you can reconstruct the Xo widgets on the Xaw library instead of MOTIF.

OPACS/v3 contains the global Makefile, NMake and descrip.mms. By default the Wo widget manager is reconstructed over MOTIF. The global Makefile (NMake, descrip.mms) triggers the stand alone makefiles of implied "o" packages.

A local Makefile (NMake, descrip.mms) includes the Config.mk (.nmk, .mms) located in Co/v3/mgr (exceptions are for W3o and HTMLo that are stand alone packages). According to the "config" and the local macros the "This.mk" (.nmk, .mms) is executed.

In case of trouble, look the environment variables in the setup files, the "configs" in the Config.mk (.nmk, .mms) files and the local makefiles for other "make" macros.

Knowing by experience that an installation could be tedious, do not hesitate to contact me (Guy Barrand) at :

     barrand@lal.in2p3.fr