• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. Enabling user environment customization using group setup...

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 143
  • Views 17635
  • Members are here 0
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

Enabling user environment customization using group setup files

jaleco
jaleco over 12 years ago

Can anyone offer insight into how to enable individual users to customize their environments when working in multiple projects, each project having multiple users, and each project having its own setup files?

Is there a specific PATH order that setup files will be loaded in, such that person A can maintain their own setup files that will be loaded before the group/project setup files, and independent of person B's personal setup files so that there are no collisions?

Or if not, is this something that could be coded into the setup files, to look for personal setup files on startup, and append them to the group/project setup file content?

  • Cancel
Parents
  • skillUser
    skillUser over 12 years ago

    I will add a small note to what Andrew has mentioned above.  You tagged your post with ".cdsenv" and ".cdsinit" so I will comment on these files.  By default the search mechanism for these files does not follow the CSF - the "caiuser" document that Andrew mentions tells you how to create a csfLookupConfig file to include these files in the CSF lookup mechanism. You can set the CDS_LOAD_ENV environment variable to control how the .cdsenv files are found and loaded, and this can have the value "CSF" which would have the same effect, but this would not alter how .cdsinit files are found.

    Hopefully the documentation covers what you need to know.

    Best regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 12 years ago

    I will add a small note to what Andrew has mentioned above.  You tagged your post with ".cdsenv" and ".cdsinit" so I will comment on these files.  By default the search mechanism for these files does not follow the CSF - the "caiuser" document that Andrew mentions tells you how to create a csfLookupConfig file to include these files in the CSF lookup mechanism. You can set the CDS_LOAD_ENV environment variable to control how the .cdsenv files are found and loaded, and this can have the value "CSF" which would have the same effect, but this would not alter how .cdsinit files are found.

    Hopefully the documentation covers what you need to know.

    Best regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information