Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 14651
  • 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

Search Path and Packages, Interface, etc.

archive

For this discussion assume a design team is used to using a search path approach to finding verilog modules and this forms the basis for the desires to follow. When an module imports a package or instances an interface, is there a similar search path convention/feature in tools like NCSIM, RC, etc?


Originally posted in cdnusers.org by bryan
Parents

  • That plus three defines are our work around for now. 1 define to include or not include. 1 define to indicate if the package has already been parsed (so its not redefined). 1 define to conditionally strip off the package and endpackages for tools that don't even support packages yet.


    Originally posted in cdnusers.org by bryan
Reply

  • That plus three defines are our work around for now. 1 define to include or not include. 1 define to indicate if the package has already been parsed (so its not redefined). 1 define to conditionally strip off the package and endpackages for tools that don't even support packages yet.


    Originally posted in cdnusers.org by bryan
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.