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

clash doesn't respect -outputdir option #125

Closed
expipiplus1 opened this issue Feb 8, 2016 · 4 comments
Closed

clash doesn't respect -outputdir option #125

expipiplus1 opened this issue Feb 8, 2016 · 4 comments

Comments

@expipiplus1
Copy link
Contributor

As far as I can tell the vhdl directory is always created in the current working directory. It would be handy to be able to redirect this output from the command line.

@christiaanb
Copy link
Member

I'll see about adding this feature to the next release, which will probably within 1.5-2 weeks.

@christiaanb
Copy link
Member

@expipiplus1 One question though: currently, files end up in vdhl/<ModuleName>; with your proposed -outputdir option, do you want files to end up in outputdir/vhdl/<ModuleName>, or in outputdir, or something else?

@expipiplus1
Copy link
Contributor Author

I'd expect things to end up in outputdir/vhdl/<ModuleName>

@christiaanb
Copy link
Member

So, in the next version of CLaSH we will have:

  • hdl files can be written to a directory (set by the -clash-hdldir flag) other than the current working directory.
    Also respects the -outputdir directory, unless:
    • -clash-hdldir is set to a different directory.
    • -hidir, -stubdir, and -dumbdir are not the same directory as -odir

christiaanb added a commit that referenced this issue Sep 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants