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

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

Parents

  • Even in a non-design managed environment, when you add a new library, you don't have the choice to add the library definition into an included cds.lib-like file; it adds it into the cds.lib (or whatever file is "forced" with ddSetForcedLib, or via -cdslib on the command line - although I'd advise against doing this because there are almost certainly assumptions in some parts of the tool that the file is called cds.lib).

    So I'm not quite sure why you decided on your methodology.

    I'm pretty certain that many DM systems recommend that you do it the way that Thomas suggested. Having a quick scan through the SOS documentation, it doesn't seem to suggest that - mainly because they support managing the cds.lib. Historically though I've always done it by managing a project.lib type file - and then manually moving the library into the project.lib when you want it managed.

    Regards,

    Andrew.

Reply

  • Even in a non-design managed environment, when you add a new library, you don't have the choice to add the library definition into an included cds.lib-like file; it adds it into the cds.lib (or whatever file is "forced" with ddSetForcedLib, or via -cdslib on the command line - although I'd advise against doing this because there are almost certainly assumptions in some parts of the tool that the file is called cds.lib).

    So I'm not quite sure why you decided on your methodology.

    I'm pretty certain that many DM systems recommend that you do it the way that Thomas suggested. Having a quick scan through the SOS documentation, it doesn't seem to suggest that - mainly because they support managing the cds.lib. Historically though I've always done it by managing a project.lib type file - and then manually moving the library into the project.lib when you want it managed.

    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.