Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Usage of '*' in verilog-library-directories #1411

Closed
veripoolbot opened this issue Mar 24, 2019 · 1 comment
Closed

Question: Usage of '*' in verilog-library-directories #1411

veripoolbot opened this issue Mar 24, 2019 · 1 comment
Labels

Comments

@veripoolbot
Copy link
Collaborator

@veripoolbot veripoolbot commented Mar 24, 2019


Author Name: ABC ABCDEF
Original Redmine Message: 2929 from https://www.veripool.org


Hi All,

Can I use '*' inside of the verilog-library-directories ?

I mean, is it possible to use just a partial file to the module location and for the rest path to use just '*'?

Ex1:
// verilog-library-directories:("." "../../ips/axi_ic/synth/") 

For Ex1, can I rewrite it as the following?
// verilog-library-directories:("." "../../ips/*") 
<pre?

Thank you!




@veripoolbot
Copy link
Collaborator Author

@veripoolbot veripoolbot commented Mar 24, 2019


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2019-03-24T12:51:49Z


You can use * to mean a single wildcard, as with all of Linux it won't do a recursive decent to subdirectories.

Note usually using verilog-library-flags is preferred as that matches simulator syntax.

    // verilog-library-flags:("-y . -y ../../ips/axi_ic/synth/") 
so this should work
    // verilog-library-flags:("-y . -y ../../ips/axi_ic/*/") 
this won't
    // verilog-library-flags:("-y . -y ../../ips/*/") 

However some simulators don't support wildcarding (with -y), and it can slow things down, so would probably discourage doing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant