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

Jump to bottom

Mdir switch does not work if presented with more than one level of uncreated directories #699

Closed
veripoolbot opened this issue Nov 25, 2013 · 2 comments
Closed

Mdir switch does not work if presented with more than one level of uncreated directories #699

veripoolbot opened this issue Nov 25, 2013 · 2 comments
Assignees
@wsnyder
Labels
area: documentation Issue involves documentation resolution: fixed Closed; fixed

Comments

@veripoolbot
Copy link
Contributor

Author Name: Ed Lander
Original Redmine Issue: 699 from https://www.veripool.org
Original Date: 2013-11-25
Original Assignee: Wilson Snyder (@wsnyder)

Hi,

I noticed a weakness with the Mdir switch a while ago, just tested it on v3.853: if you specify more than one level of hierarchy with the MDir switch, all but the last directory must already exist:

machine@17:28(277): verilator_bin -sc --error-limit 50 -y ../../view/rtl -I../../view/include --Mdir test/test --top-module top ../../view/rtl/top.v
%Error: Cannot write test/test/Vtop__Syms.h

In effect it's the same as using Unix mkdir without the -p switch; I trust a simple fix.

Cheers,
Ed
@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2013-11-25T17:41:44Z

My inclination is to document this and not fix it, as it seems a potential source of trouble if the user specifies a bad path by accident.

@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Ed Lander
Original Date: 2013-11-25T17:47:41Z

OK.

The reason we noticed it was because we were generating different output in the same object directory, but under different sub-directories (Verilating the whole the design, and also the sub-blocks):

object/top/

object/<sub_block1>/

object/<sub_block2>/

etc

Our W/A is just to precreate the sub-level of hierarchy in the Makefile.

Cheers,
Ed

@veripoolbot veripoolbot added area: documentation Issue involves documentation resolution: fixed Closed; fixed labels Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wsnyder wsnyder

Labels
area: documentation Issue involves documentation resolution: fixed Closed; fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wsnyder @veripoolbot