VersIC configuration directory

files

• versic.access - The VersIC user access control file

• versic.conf - The VersIC configuration file 
  
  (See VersIC Configuration file (versic.conf) for a full discussion of how versic.conf should be set up.)

cadence

• cdsinfo.tag - a template file used by VersIC during the creation of a new Cadence Virtuoso library

• dot_cdsenv_libmgr - sets up some gdm related variables for improving performance

• dot_cdsenv_libmgr_615 - turns off the slow DM icon overlay in IC6.15

• displayPrefs - template displayPrefs file used by VersIC to display library status

• dot_cdsinit - This should be incorporated into the site .cdsinit or, for the purposes of a standalone evaluation environment, in the Cadence Virtuoso run directory.

• dot_cdsenv_other - This is loaded automatically by the VersIC provided dot_cdsinit

• cdsLibMgr.il - This customizes the Library Manager and should be loaded from the site location - share/local directory in the Cadence installation - so that it is visible for all users. 
  
  
  • Note: It's important to keep the VersIC cdsLibMgr.il in sync with the current version of VersIC. Our recommended way of ensuring this is to place the following Skill script in the site location share/local and call it cdsLibMgr.il -

    when( VSC_INSTALL_DIR = getShellEnvVar("VSC_INSTALL_DIR")
        load(strcat(VSC_INSTALL_DIR "/config/cadence/cdsLibMgr.il"))
    )   
    

    This will ensure that the VersIC cdsLibMgr.il is always loaded from the current $VSC_INSTALL_DIR installation directory by the script cdsLibMgr.il. 
    
    
  • For evaluation purposes, cdsLibMgr.il can be placed in the directory where Cadence is started.

• cdsLibMgr_BuildIC.il - adds the BuildIC menu items to the VersIC menu pulldown

perforce

• typemap This tells how Perforce should handle locking with the various file-types in the user workspace.
  
  The default typemap sets all files to be non-mergeable, this ensures no merge conflicts in a VersIC session and is the preferred setting for inexperienced Perforce users.
  
  The contents of this file should be cut and pasted into the editor session resulting from the "p4 typemap" command.

• typemap.merge A more permissive typemap that facilitates merging for non-binary files

• protect An example Perforce protect configuration showing typical project access setup.

shell

bash/csh/envfiles

• VERSIC_P4 - Perforce and VersIC environment variables in module file syntax

• VERSIC_SVN - Subversion and VersIC environment variables in module file syntax

subversion

• config - This will be copied into the ~/.methodics/subversion at startup and used by VersIC svn commands when VSC_SVN_CONFIG_DIR is enabled in versic.conf
• A failsafe way of ensuring the Cadence files get the necessary locks in the repository (the main function of the Subversion config file in VersIC) is to copy the config file to /etc/subversion/config on user machines. This is the first place Subversion looks when determining what properties to add to new cells in the repository.