Stats

  • Locked Locked
  • Replies 9
  • Subscribers 143
  • Views 17312
  • 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

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?

Parents

  • Hi Lawrence,

    I am using a project-specific csfLookupConfig file, which has the following statements in it:

    INCLUDE .cdsinit

    INCLUDE .cdsenv

    I added INCLUDE statements for personal files -

    INCLUDE $HOME/.cdsenv

    INCLUDE $HOME/.cdsinit

    The $HOME/.cdsenv appears to get loaded, as it defines the size and location of the newly opened layout views using a leWindowBBox() setting, and this seems to work.

    However, the $HOME/.cdsinit file does NOT appear to be loaded, and this file defines the CIW with a hiResizeWindow() statement, and it is not taking effect.

    You did say the csfLookupConfig file would not work for the .cdsinit file, but I am confused how the project setup is successfully using it?

Reply

  • Hi Lawrence,

    I am using a project-specific csfLookupConfig file, which has the following statements in it:

    INCLUDE .cdsinit

    INCLUDE .cdsenv

    I added INCLUDE statements for personal files -

    INCLUDE $HOME/.cdsenv

    INCLUDE $HOME/.cdsinit

    The $HOME/.cdsenv appears to get loaded, as it defines the size and location of the newly opened layout views using a leWindowBBox() setting, and this seems to work.

    However, the $HOME/.cdsinit file does NOT appear to be loaded, and this file defines the CIW with a hiResizeWindow() statement, and it is not taking effect.

    You did say the csfLookupConfig file would not work for the .cdsinit file, but I am confused how the project setup is successfully using it?

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.