• 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 Design
  3. Keeping Library colors in Library Manager

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 15669
  • 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

Keeping Library colors in Library Manager

GoRangers
GoRangers over 13 years ago

Hi,

I noticed IC6.1's new feature to allow you to "ASSIGN libname DISPLAY colorname".   It works, but you have to hand-hack the cds.lib.

 But I'm coding some library utilities which utilize the ccp functions, and I want to retain the colors whenever I copy/rename a library.  All the ASSIGN statements get orphaned whenever I move libraries around via ccp.   How do I keep the ASSIGN statements in lockstep with my ccp operations?    Do I actually have to open the cds.lib file as an ASCII and sed/grep everything with a series of system calls from Skill??  

 Surely someone has hit this before?   When your ASSIGN statements all get orphaned, that's pretty bad.

thanks

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago
    What was the SR number? I'll take a look. I agree with you - it should be managed as part of copying/renaming the library.

    The SKILL API would be a useful enh too, but not so necessary if it did the right thing.

    Thanks,

    Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 12 years ago
    What was the SR number? I'll take a look. I agree with you - it should be managed as part of copying/renaming the library.

    The SKILL API would be a useful enh too, but not so necessary if it did the right thing.

    Thanks,

    Andrew
    • 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