Stats

  • Locked Locked
  • Replies 2
  • Subscribers 163
  • Views 19094
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

env file search path

archive

Is there any way of changing the env file search path?
Allegro normally looks for the env file at :
cds_inst_dir\share\pcb\text

What I'd like to do is create a heirarchy, where Allegro first looks for the env file on a network drive, then, if it doesn't find one (probably because the user doesn't have the networked drive) Allegro drops back to the secondary (original) path.

That way, all our standalone users can share a common env file whilst working on the office, but are not prohibited from working stand alone.

Anyone?
Thanks,


Originally posted in cdnusers.org by vealmic@uk.ibm.com
  • archive

    Check the CDS_SITE documentation in the Cadence Allegro documentation. You can create an env file containing
    company default settings that will be seen by all users if you use a central file model. By default, Allegro will look
    for a company env file @ /share/local/pcb/env but you can override the location by settings a CDS_SITE
    OS level variable. This is the recommended method since it does not require you to modify anything in the
    user's environment unless you want to unlink the CDS_SITE default location from the Cadence install hierarchy.

    Alternatively, you can add to a user's own env file the ability to read additional env files. If you want to suppress
    the warning when it cannot find an env file use the "-q" option. Example: source -q . Conditional
    reads can be accomplished use the "ifnvar" statement. If a env is read it sets a "well known" variable then
    additional sourcing can be suppressed. Example
    source -q
    # if network source was succesful then that env file will set the variable; env_success
    # if didn't read then source a local env file
    ifnvar env_success "source -q

    For more info see
    http://www.cdnusers.org/community/allegro/Resources/resources_PCB/lr/sTP_cdnlive2005_1285farmar.pdf


    Originally posted in cdnusers.org by fxf
  • archive

    Thanks! I'll give it a go.


    Originally posted in cdnusers.org by vealmic@uk.ibm.com
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.