• 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. Check out cds.lib fails

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 144
  • Views 20796
  • 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

Check out cds.lib fails

acook
acook over 12 years ago

Andrew,

My enviornment uses the clio DM system. When I go to create a new library, Cadence asks for the cds.lib to checkout. A lot of times the managed file is locked and I cannot edit it. For this reason I create a non-managed "cds_custom.lib" that I include in my "cds.lib". If I specify a filename that is not "cds.lib" in the"Check out cds.lib" form that comes up, it fails to edit anything and I cannot create a library.

Two Questions:

 Is this a DM bug or Cadence bug?

If it is a Cadence bug, it seems trivial enough to change to allow any file name to be modified, as in my example a user may need to modify a referenced library file in the same path as the cds.lib.

 Thank you,

Aaron

  • Cancel
Parents
  • TeeBro
    TeeBro over 12 years ago

     Hi Aaron,

    I think the probelm is the way the environment was set up.  The cds.lib should be for the user and not shared by the group.  Usually the environment is set up so that the cds.lib sources another file that is managed.  For example, the users cds.lib (unmanaged) sources a project_cds.lib (managed) that contains the libraries used for the project you are working in.  If a library needs to be updated for the group then the project_cds.lib is edited and checked in and everyone is updated next time they start the tool.

     

    Thomas

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

     Hi Aaron,

    I think the probelm is the way the environment was set up.  The cds.lib should be for the user and not shared by the group.  Usually the environment is set up so that the cds.lib sources another file that is managed.  For example, the users cds.lib (unmanaged) sources a project_cds.lib (managed) that contains the libraries used for the project you are working in.  If a library needs to be updated for the group then the project_cds.lib is edited and checked in and everyone is updated next time they start the tool.

     

    Thomas

    • 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