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

Stale files in vhdl folder #96

Closed
ggreif opened this issue Nov 25, 2015 · 3 comments
Closed

Stale files in vhdl folder #96

ggreif opened this issue Nov 25, 2015 · 3 comments

Comments

@ggreif
Copy link
Contributor

ggreif commented Nov 25, 2015

When iterating a design sometimes stale files remain in vhdl/* (and other) folders. It would be nice to have an extension to the synthesis commands :vhdl that clean out stale files.
Would :vhdl-clean or :vhdl -clean work?

@christiaanb
Copy link
Member

We used to do this by default, but somehow this feature got dropped when we switched to supporting multiple backends. I prefer that cleaning up would be the default again.

So in interactive mode we would have: :vhdl [noclean], where the square brackets indicate that it is an optional argument.

In batch mode we would have -clash-noclean flag. So you'd say: clash --vhdl -clash-noclean <MODULE.hs>.

I'll implement this soon, probably by tomorrow already.

@ggreif
Copy link
Contributor Author

ggreif commented Nov 25, 2015

woot!

@christiaanb
Copy link
Member

OK, slight change of what I said earlier. There's one static flag: -clash-noclean, which tells CLaSH NOT to clean up existing HDL files, and it applies to both the interactive and the batch modes. That is, there is no additional option for the interactive :vhdl command.

Being a static flag, it can only be supplied when you start the clash compiler. So you cannot do :set -clash-noclean in interactive mode.

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

No branches or pull requests

2 participants