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

  •  James,

    That's not the way that the csfLookupConfig works. It controls whether a type of file is found using the CSF mechanism or not, and doesn't tell it locations where to find/read a file.

    So if you have:

    INCLUDE .cdsenv
    INCLUDE .cdsinit

    it tells it that both of these files will look in the setup.loc locations for each file - that is not the default behaviour for these files (for historical reasons, because both files pre-date the CSF mechanism being introduced).

    With .cdsenv, it will load all the files that it finds in setup.loc locations, with the top-most entry in the setup.loc winning over the lower level entries - so that the first is the most-specific.

    With the .cdsinit, it loads the first file found only. If you want to load the others, you'd need to carry on the search yourself for other locations to load from, but you can encode that in some central .cdsinit yourself to have the logic where to look.

    Regards,

    Andrew.

Reply

  •  James,

    That's not the way that the csfLookupConfig works. It controls whether a type of file is found using the CSF mechanism or not, and doesn't tell it locations where to find/read a file.

    So if you have:

    INCLUDE .cdsenv
    INCLUDE .cdsinit

    it tells it that both of these files will look in the setup.loc locations for each file - that is not the default behaviour for these files (for historical reasons, because both files pre-date the CSF mechanism being introduced).

    With .cdsenv, it will load all the files that it finds in setup.loc locations, with the top-most entry in the setup.loc winning over the lower level entries - so that the first is the most-specific.

    With the .cdsinit, it loads the first file found only. If you want to load the others, you'd need to carry on the search yourself for other locations to load from, but you can encode that in some central .cdsinit yourself to have the logic where to look.

    Regards,

    Andrew.

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.