-
Notifications
You must be signed in to change notification settings - Fork 199
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
how to run chisel-tutorial in the IntelliJ IDE with Scala and SBT plug-ins? #149
Comments
facing the same! please give some solution to this. How can we run this tutorial in the IntelliJ scala environment? |
Not super elegant, but you can use the terminal in the IntelliJ editor to type the sbt commands to run your code. So you can still use IntelliJ for editing (that's my default development setup).
There is also a sbt window available within IntelliJ that you can use, it just takes some time to start.
Cheers,
Martin
… On 17 Oct 2019, at 05:59, Shraddha Devaiya ***@***.***> wrote:
facing the same! please give some solution to this. How can we run this tutorial in the IntelliJ scala environment?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
when I execute the command 'run' in sbt command window to build the definition, it is giving me an error like the following: [error] stack trace is suppressed; run 'last update' for the full output [error] not found: C:\Users\Pvips_Admin.ivy2\local\edu.berkeley.cs\chisel-iotesters_2.13 so what can I do for this? |
Hello, It is working fine now. there was one JDK version error, it is supported JDK 11.0 and I had configured JDK 13.0. |
I imported the chisel-tutorial into IntelliJ and it recognized the sbt project. Inside the sbt console I can successfully run the builds and tests, but when I try to use the editor, the environment can't resolve the chisel3 import.
Being new to scala, sbt, chisel, and the IntelliJ scala/sbt environment, I need a little help finding the pieces in the environment that are not configured correctly.
The text was updated successfully, but these errors were encountered: