Stats

  • Replies 3
  • Subscribers 160
  • Views 26337
  • Members are here 0
More Content

How to find out which env file is being used?

thewill2live

Hey guys,

 

I edited my scriptpath in the global ENV file (located in the CDSROOT/share/pcb/text/ directory) as well as the local ENV file (located in the  CDSROOT/pcbenv/ directory) both to have a new entry for the scriptpath. Yet after loading up Allegro and clicking on Tools>Utilities>Env Variables it still shows that my scriptpath is set to some other directory (that is not listed in either of the two aformentioned ENV files).

 So my question is, is there some way to find out which ENV file is getting loaded by Allegro (besides manually looking up any and all ENV files in the directory)? This specific computer I'm talking about does have older versions of Allegro also installed on it, is it possible that it defaults to the oldest version's global ENV?

 

Thanks for any help you can give me. 

Parents
  • fxffxf

    If you manually edit your local env file place your edits as shown below (LOCAL ENV FILE),

     It is also not a good idea to override the Cadence supplied values in SCRIPTPATH. It is best to insert your entries in the front by:   set scriptpath = <your stuff> $scriptpath

    The env file attempts to read a site specific env file located at <cdsroot>/share/local/pcb/site.env.

    By default the env files are read in the follow order with 1 and 2 controll via the "source $TELENV" in the user's local env file

    1.     <cadence supplied> --- cdsroot/share/pcb/text/env
    2.      <company or site supplied>  -- cdsroot/share/local/pcb/site.env
    3.      <user supplied>        --- <home>/pcbenv/env

     

    -- LOCAL ENV FILE ---

     source $TELENV

    <<<<<  Put all your manual edits here >>>>

    ### User Preferences section 

Reply
  • fxffxf

    If you manually edit your local env file place your edits as shown below (LOCAL ENV FILE),

     It is also not a good idea to override the Cadence supplied values in SCRIPTPATH. It is best to insert your entries in the front by:   set scriptpath = <your stuff> $scriptpath

    The env file attempts to read a site specific env file located at <cdsroot>/share/local/pcb/site.env.

    By default the env files are read in the follow order with 1 and 2 controll via the "source $TELENV" in the user's local env file

    1.     <cadence supplied> --- cdsroot/share/pcb/text/env
    2.      <company or site supplied>  -- cdsroot/share/local/pcb/site.env
    3.      <user supplied>        --- <home>/pcbenv/env

     

    -- LOCAL ENV FILE ---

     source $TELENV

    <<<<<  Put all your manual edits here >>>>

    ### User Preferences section 

Children
No Data
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.