Alpha_1 Programmers's Manual

Getting Started for Alpha_1 Developers

• Don't set A1ROOT. The set-envars script will do it for you.
• Source /res/gdc/projects/general/cmds/set-envars and $gPRJ/alpha1/cmds/set-envars instead of $A1ROOT/exec-envars in the .cshrc.
• To establish an Alpha_1 working tree, insert a line like this BEFORE sourcing the Alpha_1 set-envars:

  	setenv A1WRK $gWRK/alpha1
  
   Consider adding this line, before sourcing set-envars:
  	setenv A1_USE_ENVARS yes
  	
  This will cause the Alpha_1 source directory variables listed in
  $a$cmds/dir.vars to be set as environment variables instead of shell
  variables.  The advantage is that environment variables like $cmds will then
  be usable in Emacs.
  
   Load alpha1 instead of a1 in the .emacs, like this:
  (condition-case ()
      (load (substitute-in-file-name "gPRJ/emacs/gdc_general"))
    (error (message "Can't load gdc_general.el")))
  (condition-case ()
      (load (substitute-in-file-name "$A1SRC/emacs/alpha1"))
    (error (message "Can't load alpha1.el")))
  
  Among other things, this will make the
  Alpha_1 Tags
  available for navigating your way around the Alpha_1 sources. 
  
   Consider sourcing the $a$cmds/set-path script to maintain your
  execution search path.  Set-path contains the necessary directories, in the
  proper order, so that Alpha_1 makes will work correctly.  It is also kept up
  to date as the set of directories changes from time to time on the various
  Unix system Alpha_1 runs on.