Stats

  • Locked Locked
  • Replies 4
  • Subscribers 62
  • Views 16627
  • 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

Reading HDL files in RC

archive

Hi.
I'm having problems migrating from DC to RC in terms of reading HDL files.

1. I have a directory with subdirectories which include .v files - when I specify the main directory as the HDL search path, RC doesn't read the .v files under the subdirectories - any idea why?
The manual says it works like the search in unix therefore I don't understand why it doesn't try to read the subdirectories.
2. I have .v files which have commands like `include ../../ - when running RC, RC moves to a directory of its own with no regard to where the command was run from (unlike DC where if I run it from a certain directory, this directory is the reference for finding other files in case I use realtive statements such as ..) - therefore, those realtive `include commands doesn't work - any idea how to solve the problem?

Thank you in advance,
Adi.


Originally posted in cdnusers.org by adi_j
Parents

  • adi_j,
    As you have surmised, RC will not look at subdirectories recursively to find the HDL files, you will have to specify each subdirectory in the hdl_search_path attribute in order to get RC to look for source code in those directories. As for your second question, make sure that when you set the hdl_search_path attribute, you include "." in the path, otherwise the relative paths will on search for HDL starting at the places you specify in hdl_search_path. So in order to get these to work, do the following:

    set_attr hdl_search_path {. /home/my_proj/hdl_dir_name}

    Hope this helps.


    Originally posted in cdnusers.org by jflieder
Reply

  • adi_j,
    As you have surmised, RC will not look at subdirectories recursively to find the HDL files, you will have to specify each subdirectory in the hdl_search_path attribute in order to get RC to look for source code in those directories. As for your second question, make sure that when you set the hdl_search_path attribute, you include "." in the path, otherwise the relative paths will on search for HDL starting at the places you specify in hdl_search_path. So in order to get these to work, do the following:

    set_attr hdl_search_path {. /home/my_proj/hdl_dir_name}

    Hope this helps.


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