Application Directories - Structures, Configurations and Builds

• Location

  Each application resides in its own top level directory under the /home/epicssm directory.
  
  For example LIRIS is located at /home/epicssm/liris.

  The application modules required for each application are checked out from CVS.
  
  For example INGRID requires ingridApp, geminiApp and motorApp.

  When an instrument is fully functional there will be a development directory for modifications.
  
  For example INGRID has the ingridDev directory.

• Build

  We currently build for 2 different VME CPU Cards a MVME147 and a MVME167.
  
  To allow us to do this an environment variable is set. This variable is CROSS_COMPILER_TARGET_ARCHS and is located in the applications config/CONFIG file.
  
  For example the WYFFOS application configuration is at /home/epicssm/wyfffos/config/CONFIG.
  
  It currently uses a MVME147 CPU so the environment CROSS_COMPILER_TARGET_ARCHS=147 is defined.

  The total application is built from the application directory.
  
  For example to build INGRID:-

  • cd /home/epicssm/ingrid
  • gmake clean
  • gmake

  This will build ingridApp, geminiApp and motorApp.

  Each application can be built individually by changing to the individual application directory
  
  For example to build the motorApp for INGRID:-

  • cd /home/epicssm/ingrid/motorApp
  • gmake clean
  • gmake

  For software development of an existing instrument the instrumentDev directory is used by changing to the applications development directory
  
  For example to build the development version of USP:-

  • cd /home/epicssm/usp/uspDev
  • gmake clean
  • gmake

  For the development software to be installed in the VME crate it is necessary to reboot the VME crate.
  
  To reinstall the released software it is necessary to rebuild from the /home/epicssm/usp/uspApp directory

• Software Control

  All EPICS software is under CVS control, and as modifications are made the files should be commited to the CVS repository.
  
  The tkcvs GUI program can be used for this.
  
  Further information on using CVS is available at GEN-CVS-1: Using CVS at the ING

• Software Release

  The bootscript, generally called st.cmd, are in src and get installed in the vxworks directory. It is necessary to edit those because they reflect dependencies to current path setting when booting the VME racks.

  • Comprehensive documentation can be found here:-
    
    EPICS IOC Applications Building and Source Release Control

© 2004 by Issac Newton Group - email Epics Software Manager All rights reserved.

Last modified: Mon Feb 23 17:05:29 WET 2004