• 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. Logic Design
  3. Procedure to define a new VHDL library in RTL compiler ...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 62
  • Views 15050
  • 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

Procedure to define a new VHDL library in RTL compiler script

shustar
shustar over 13 years ago

Could someone please let me know the RTL complier command to define a new VHDL library? And where should the new library packages be placed? Should the be placed in the same run directory or can we include the path in the compile script?

  • Cancel
  • grasshopper
    grasshopper over 13 years ago

    Hi shustar,

    VHDL libraries do not have to be in same directory as scripts. HDL in general relies on attribute hdl_search_path when an absolute path is not provided . read_hdl -library switch which can be used to specify what library a given set of VHDL files should go to.

     gh- 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • shustar
    shustar over 13 years ago

     thanks!

    One more question, do we need to explicitly define a new library (say newLib), or just the command "read_hdl -vhdl -library newLib" is sufficient to define the new library?

    I could not find any command for this in the RC user manual.

    -ss

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • grasshopper
    grasshopper over 13 years ago
    Hi shustar, there is no command needed to create the libraries. -library.... infers that you need to create it if it does not exist gh-
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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